Identity Resolution

From anonymous impression to a named customer record

Demo mode

Viewer

Someone who saw the ad but did not click.

No data available

What we capture

  • Nothing. The advertising platform reports impressions and frequency in aggregate only.

What we cannot capture

  • Whether a specific person saw the ad.
  • How many times they saw it.
  • Any link between an impression and a later visit. There is no per person data at this layer from any platform.

Visitor

Someone who clicked an ad and landed on the site, but has not identified themselves.

2

What we capture

  • Campaign id, adset id and ad id.
  • The click identifier (fbclid or gclid).
  • The full landing URL and the timestamp, all read directly from the URL.

What we cannot capture

  • Who the person is.
  • A repeat visit can be recognised on the same device through a first party cookie, but it cannot be attributed to a named person, and it does not carry across devices.

Lead

Someone who has submitted their details through a form, WhatsApp or Instagram.

4

What we capture

  • Everything at Visitor level, now attached to a named record.
  • Name, phone and email.
  • Earlier anonymous touches from the same session are merged retroactively onto the record.

What we cannot capture

  • Touches that happened on a different device before identification.

Customer

An identified person with at least one completed booking.

6

What we capture

  • Everything at Lead level, plus vehicles, service history and lifetime value.
  • Every subsequent ad click is attributed to this person, including different ads on different days.

No remaining limits

  • Nothing further at this layer. This is where per person ad frequency becomes fully answerable.

How an anonymous click becomes a named customer

Andi Setiawan, reconstructed from the records stored against him.

  1. 14-06-2026 09.12Visitor

    Visitor. Not yet identified.

    Ad 23859102847612 on Meta, campaign 23859102847610

    https://demo.example.id/servis-berkala?fbclid=IwAR2xQ9&campaign_id=23859102847610&adset_id=23859102847611&ad_id=23859102847612

  2. 14-06-2026 09.14Lead

    Identity resolved. The earlier click is now attached to this person.

    Booking request form: Toyota Avanza 2019, plat B 1234 ABC, servis berkala, cabang Flagship Kelapa Gading, preferensi Selasa pagi.

  3. 16-06-2026 09.00Customer

    Customer.

    Completed booking bkg_01

  4. 02-08-2026 19.44Customer

    Attributed on arrival, because the person is known.

    Ad 70012345678 on Google, campaign 21447890123

    https://demo.example.id/servis-rem?gclid=Cj0KCQ&campaign_id=21447890123&adset_id=17654321098&ad_id=70012345678

  5. 20-08-2026 21.03Customer

    Attributed on arrival, because the person is known.

    Ad 23859334410024 on Meta, campaign 23859334410022

    https://demo.example.id/promo-rem?fbclid=IwAR7pL1&campaign_id=23859334410022&adset_id=23859334410023&ad_id=23859334410024

Gap between the first ad touch and the form submission that resolved it: 2 minutes.

Ad frequency, answered at the layer where it is possible

CustomerTouchesPlatformsDetail
Andi Setiawan3Meta, Google
  • 14-06-2026 09.12 · Meta · campaign 23859102847610 · ad 23859102847612
  • 02-08-2026 19.44 · Google · campaign 21447890123 · ad 70012345678
  • 20-08-2026 21.03 · Meta · campaign 23859334410022 · ad 23859334410024
Ratna Dewi2Meta
  • 27-04-2026 08.22 · Meta · campaign 23858990112233 · ad 23858990112235
  • 23-08-2026 19.48 · Meta · campaign 23859334410022 · ad 23859334410077

This is exactly the question that cannot be answered at Viewer or Visitor level, and can be answered completely from Lead level onward.

Unresolved visitors

  • 26-08-2026 07.39Googlecampaign 21447890123 · ad 70012345678

    https://demo.example.id/servis-rem?gclid=Cj0KQQ&campaign_id=21447890123&adset_id=17654321098&ad_id=70012345678

    Same ad, one identified and one not. Ad 70012345678 also produced a named touch from Andi Setiawan.
  • 25-08-2026 20.11Metacampaign 23859334410022 · ad 23859334410024

    https://demo.example.id/promo-rem?fbclid=IwAR3nQ2&campaign_id=23859334410022&adset_id=23859334410023&ad_id=23859334410024

    Same ad, one identified and one not. Ad 23859334410024 also produced a named touch from Andi Setiawan.

These clicks are captured and stored. If any of these people later submit a form or message on WhatsApp within the same session, their click history attaches to them retroactively. Until then they remain at Visitor level and are counted, not named.

Card A: URL parameter capture

How it works
Campaign, adset and ad identifiers are read from the landing page URL when the visitor arrives.
Requires
Campaign URLs built with the parameters included, set once per campaign.
Does not require
Platform business verification, or any third party automation tool.
Limit
Only works when the ad sends traffic to the website. It captures nothing for in platform lead forms or click to message ads.

Card B: Platform Marketing API

How it works
A direct connection to the advertising platform pulls campaign structure and results.
Requires
A one time business verification on the platform side. After that verification, accounts connect without further manual setup and without a third party tool.
Does not require
Parameters in campaign URLs.
Limit
The one time verification is a prerequisite and depends on the advertiser, not on the software.

In practice these are combined. URL capture covers website traffic from day one, and the API adds campaign level reporting once verification is complete.

Identification happens when a person voluntarily provides their details. Anonymous visitor data is limited to campaign parameters and technical session data. Consent handling and retention are configured per deployment in line with Indonesian personal data protection requirements.