How to track chat conversation to qualified lead for Pinterest Ads

Architecture

The exact event sequence

Five stages. The break is at the widget boundary. Chat platforms run their own scripts and store their own session state, and unless the click identifier is explicitly passed into the conversation's metadata, the CRM contact that results has no trace of the campaign that produced it. The identifier has to survive all of them.

1. Step 1

   Chat opened

   The widget was engaged. Volume only, and dominated by existing customers.

2. Step 2

   Conversation started

   A real exchange rather than a bounce off the greeting.

3. Step 3

   Qualified as a sales conversation

   Your team's judgment, not the widget's. This is the first meaningful signal.

4. Step 4

   Contact created in the CRM

   The lead exists as a record that can be attributed and followed.

5. Step 5

   Opportunity or booking created

   The money-adjacent event, wherever your funnel goes next.

Diagnostic sequence

What's specific to Pinterest Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Pinterest Ads.

1. 1

   Click identifier: the epik click identifier

   Pinterest appends epik to your landing page URL and the tag stores it in the _epik cookie. It is a single parameter rather than Google's three, which makes capture simpler — but Pinterest traffic skews heavily to iOS and to saved Pins opened weeks after they were first seen, so the identifier frequently arrives on a visit that is nowhere near the conversion. Persist it server-side the moment you see it.

2. 2

   Import mechanism: the Conversions API

   Server events posted to Pinterest's Conversions API, carrying the click identifier where you have it plus hashed customer information. Pinterest's API has been through more than one revision — check the current endpoint and required field names against Pinterest's own documentation before building, rather than trusting an older integration guide.

3. 3

   Deduplication

   Same shape as Meta: the browser tag and the Conversions API event must carry the same event_id for the same conversion, and the event name must match too. Send both without pairing them and every conversion counts twice. This is worth testing deliberately, because Pinterest volumes are often low enough that a doubling looks like a good week rather than a bug.

4. 4

   Window and timing

   Pinterest's attribution windows are configurable per campaign and separate the click path from the engagement and view paths, which is unusual. Confirm which window your reporting is set to before comparing anything, and verify the accepted event-freshness limit for server events against Pinterest's current documentation.

5. 5

   The Pinterest gotcha

   Pinterest is a save-now-buy-later platform in a way the other networks are not. A Pin saved in October and acted on in December is normal behavior, and it sits far outside any sensible click window — so a share of genuine Pinterest-driven revenue is structurally unattributable no matter how good the build is. Say that out loud before anyone sets a target.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Pinterest ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the conversation record in your chat platform, joined to the CRM contact it created after a full real journey through every step.
• Opportunity or booking created confirmed arriving at Pinterest Ads, verified by the event delivery and match reporting inside Pinterest Ads Manager, not the API response code.
• Your crm's contacts created from chat, filtered to the qualification your team actually applies reconciled against Pinterest Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If your chat is purely a support channel and never produces sales conversations, there is nothing here to attribute and we will say so rather than build it.
• If Pinterest is a small test line on your media plan, the Conversions API is more work than the signal is worth this quarter. It earns its keep when Pinterest is a channel you are actually scaling.
• If your cycle from click to opportunity or booking created regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward CRM contacts created from chat, with a qualification flag instead and use the later data for budget decisions rather than for bidding.
• If almost none of your conversation records carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.