TheADX solution

BDDK-Compliant Programmatic Advertising for Banks and Finance (TheADX)

Banks often stall on programmatic advertising not because of creative or budget, but because of data: if information security does not approve what data an ad tag on the site carries and where, the campaign does not start. TheADX's claim targets exactly this point: the company states it is the first local DSP fully compliant with BDDK (Türkiye's banking regulator) requirements. We set up this structure with bank teams by documenting the data flow.

Book a growth call Read the details

Illustrative view: illustrative view of a display ad for a finance brand.

Purpose and appearance

What do we use this format for?

The starting point of this solution is letting banks that stopped programmatic advertising because of information security policy open campaigns again while keeping data in the country. For products such as credit cards, loans and deposits, we aim to collect applications, exclude applicants quickly and cross-sell suitable products to existing customers.

Funnel stages it serves

Awareness
Consideration
Conversion
Loyalty

What TheADX's finance solution promises

The points below are statements from TheADX's own finance page. For a bank's compliance team, what matters is where data is stored and who it is shared with. According to the company, data from pre-login and post-login internet banking pages is hosted on servers in Türkiye, in line with BDDK regulation.

A DSP and SSP developed in Türkiye, compliant with BDDK requirements
Data hosted in Türkiye; compliance with KVKK (Türkiye's personal data protection law) and GDPR
Private SSP infrastructure: data is not shared with multiple SSPs
Segment management that automatically removes users who have taken up the offer

Questions a bank's information security team asks

For financial brands, information security approval often sets the campaign timeline. So before any code is installed, we prepare a data flow document: which code goes on which page, which event is sent, whether outgoing data contains personal data or customer numbers, which server stores the data and for how long. On post-login pages, meaning inside internet banking, we keep the scope of the ad code especially narrow.

What delays approval most is other foreign-based ad tags already running on the same site. Moving to a local DSP does not solve the data flow problem by itself while those tags stay on the page. We first take an inventory of tags in Google Tag Manager and report which ones fire on post-login pages.

Targeting and ad fatigue in financial services campaigns

In banking products, showing ads to the same user after they have taken the product is both wasted budget and a customer experience problem. TheADX states that its segment management can automatically remove users who took up an offer from the segment. We use this for one-off products such as credit card applications or deposit account openings, so applicants are excluded right away.

For cookieless targeting, the platform says it offers a UID2 operator service. Because UID2 uses an encrypted form of an identifier such as email, we decide together with the bank which identifier it can share and on what legal basis under KVKK. For post-conversion analysis, we check the bank's data localization policy before moving raw data into a foreign cloud environment such as BigQuery.

Which regulation applies to which institution?

BDDK compliance matters for banks and institutions under BDDK supervision. Payment and electronic money institutions are supervised by the Central Bank of the Republic of Türkiye (TCMB), and the rules for them can differ. So before starting a campaign, we confirm with the institution's legal team which regulation applies. We cover the general platform on our TheADX page and the Google ecosystem alternative on our Display & Video 360 page.

BDDK-Compliant Programmatic for Finance: when do we recommend it?

We recommend it

Banks whose information security policy does not allow foreign ad tags
Financial institutions that want to cross-sell based on post-login behavior
Brands that want to exclude applicants quickly for one-off products such as credit cards, loans and deposits

We don't recommend it

Fintech brands outside BDDK scope with no barrier to using global DSPs
Institutions that will keep foreign-based ad tags on their site; tag cleanup comes first
Institutions that already have information security approval to process campaign data with a global DSP

How we manage BDDK-Compliant Programmatic for Finance

Regulation and scopeWith the legal team, we confirm whether the institution is under BDDK or TCMB supervision and which pages are in scope.
Tag inventoryWe list all ad and analytics tags on the site and report those firing on post-login pages.
Data flow documentWe document the events, fields and storage location for the TheADX code and submit it for information security approval.
Segments and exclusionsWe build segments per product that automatically remove users who completed an application.
Compliant reportingWe use aggregated metrics in reports, with no personal data.

BDDK-Compliant Programmatic for Finance: metrics and requirements

Metrics we track

Cost per application
Application completion rate
Viewable impressions
Frequency
Users removed from segments
Performance by publisher

What you need to get started

Code installation approval from information security and legal teams
An up-to-date list of tags on the site
Definitions of conversion events such as applications and account openings
Approved creative copy that meets financial advertising regulations

Official sources

The Brand Move TheADX Team

To learn more about BDDK-Compliant Programmatic for Finance or other TheADX ad formats, contact The Brand Move TheADX team today.

Explore further

Other TheADX campaign types and ad formats

TheADX overview

TheADX DSP (Display, Video, Native)

Display, video, native and masthead on web and apps. Local campaigns with neighborhood-level location and keyword targeting.

Explore

Audio Ads

Programmatic audio ads on music streaming, podcasts and digital radio, targeted by time of day, device and listening habits.

Explore

Frequently asked questions

BDDK-Compliant Programmatic for Finance: frequently asked questions

Does using TheADX make our bank BDDK compliant automatically?

No. TheADX states that its own infrastructure meets BDDK requirements, but compliance is assessed together with the bank's whole site and data setup. If other tags on the site send data abroad, the issue remains. That is why we treat the tag inventory as the first step.

Can ad tags be used on post-login pages?

TheADX states that pre-login and post-login data is hosted in Türkiye. Still, the bank's information security team decides which events are sent from post-login pages. We usually recommend starting only with events that contain no personal data, such as product interest.

Is it suitable for payment institutions and fintechs?

It can be, but payment and electronic money institutions are supervised by TCMB and the rules can differ. We confirm with the institution's legal team which regulation applies before recommending a local or global DSP.

Why do banks in Türkiye struggle with programmatic advertising?

Mainly because of data: information security teams need to know what data each ad tag sends, where it is stored and who it is shared with. Foreign-based tags often fail that review, which is the gap a local DSP that hosts data in Türkiye aims to fill.

How do you stop showing ads to customers who already applied?

With segment rules that remove users from the target segment as soon as they complete an application or open an account. TheADX states this can happen automatically; we set it up per product and check segment counts in reports.

Let's run a first BDDK-Compliant Programmatic for Finance review together.

In a free call we review your audience, inventory needs and measurement setup, then tell you in writing which platform makes sense to start with.

Book a growth call No sales pressure. Just findings.