Pixelflow
Troubleshooting

How does PixelFlow know which ad to credit for an event?

PixelFlow does not decide ad attribution on its own. Its job is to capture the Meta click identifier when someone lands from a Facebook or Instagram ad, keep that identifier available for later events, and send it back to Meta with those events. Meta then uses that data to match the event to the ad click inside its own attribution system.

If you want the technical details of how PixelFlow stores Facebook click IDs, see How does PixelFlow handle Facebook click IDs (fbclid)?.

What happens when someone clicks your ad

When a visitor clicks a Meta ad, the landing page URL can include an fbclid parameter. PixelFlow reads that value in the browser and formats it into Meta's click ID format. It then persists that value so it can still be used on later events instead of only on the first page view.

PixelFlow also sends browser matching data such as fbp. Together, these values give Meta stronger signals for connecting later events back to the original ad interaction.

How PixelFlow connects later events back to the ad click

After the first visit, the customer may keep browsing, view more pages, submit a form, or complete a purchase later. When PixelFlow sends those events, it includes the stored click identifier with the event payload. On the backend, PixelFlow processes that click ID as fbc, which is Meta's click ID field.

That means the event sent later does not need to happen on the same page as the original ad click. As long as the click ID is still available and the event is sent to Meta, Meta can use it as a strong attribution signal.

Example: ad click, ViewContent, then Stripe Purchase

  1. A person clicks your Facebook ad.

  2. They land on your site with an fbclid in the URL.

  3. PixelFlow captures that fbclid, stores it, and prepares it for later Meta event matching.

  4. The person views a product or offer page. PixelFlow can send a ViewContent event for that page view.

  5. Later, the same person completes checkout through your Stripe payment flow.

  6. When Stripe confirms the payment, PixelFlow sends a server-side Purchase event to Meta through CAPI.

  7. That later Purchase event can include the stored click ID data from the original ad visit, so Meta can match the conversion back to the ad click.

In simple terms: the ad click creates the attribution clue, PixelFlow keeps that clue available, and later events such as ViewContent and Purchase send it back to Meta.

Why this matters for Stripe purchases

Stripe checkout often happens after the first landing-page visit, and sometimes after several pages of browsing. If you only relied on the original page URL, that purchase could be harder to connect back to the ad. PixelFlow closes that gap by preserving the Meta click identifier and including it when the Stripe Purchase event is sent.

That is why a purchase can still be attributed even though the buyer did not convert immediately after clicking the ad.

Does PixelFlow send the fbclid back to Facebook?

Yes. PixelFlow captures the original fbclid, converts it into the format Meta expects for click attribution, and sends that click ID back with later events. In PixelFlow's event processing, that canonical field is handled as fbc.

Meta uses that returned click ID, along with other matching signals such as fbp, to decide whether the event should be credited to a prior ad interaction.

What PixelFlow does vs. what Meta does

  • PixelFlow: captures the click ID, persists it, and sends it with browser and server-side events such as ViewContent and Stripe Purchase.

  • Meta: decides whether that event should be credited to a campaign, ad set, or ad based on its own attribution rules and windows.

If an event appears in Events Manager but attribution in Ads Manager looks different, see Why doesn't Facebook attribute events to a specific campaign?.

Was this helpful?