_fbp created
A post-click same-origin request carries both _fbp and fbp_auto_set.
_fbc absent
The page only creates it from fbclid, which this landing URL did not have.
IDs not redirected
The actual AppsFlyer click contains no fbp, fbc, or fbclid.
No Meta event beacon
The Meta connection failed and no facebook.com/tr request appears in the HAR.
Ad Library verified
The destination in the HAR exactly matches an active ad in Meta's official library, including its campaign-specific dance deep link.
Exact active ad
- Library ID: 1768878227328932
- Advertiser: AI Video Generator
- Active since July 6, 2026
- Primary text: “💃 Make anyone dance with AI Video”
- Headline: “🤣🕺 Join AI Dance Trend”
- CTA: Download
- Display domain:
AIVIDEOART.CO
Facebook wrapper behavior
The CTA uses l.facebook.com/l.php, whose encoded destination is the exact get-started-v5?target=meta&deep_link_value=genericDance URL.
The wrapper refreshes to that destination without adding fbclid, fbp, fbc, or UTM parameters. The missing fbclid is therefore expected for this Ad Library preview link.
What the HAR can and cannot prove
The capture confirms that the official Ad Library destination was opened. It does not contain the preceding l.facebook.com request, and it does contain a Safari/Google autocomplete lookup for the full destination immediately before navigation. It therefore cannot prove whether the CTA was clicked directly or the destination was copied or entered in Safari.
Captured sequence
The initial page is a 200 response with an internal Next.js rewrite. The only browser-visible HTTP redirect occurs later at AppsFlyer.
| UTC time | Evidence |
|---|---|
| 21:04:13.569 | Landing document returns HTTP 200. The response sets only the existing project cookie. |
| 21:04:18.148 | connect.facebook.net fails with Proxyman status 999 (Error). |
| 21:04:18.653 | AppsFlyer OneLink is requested without fbp, fbc, or fbclid. |
| 21:04:18.697 | First-party telemetry records “Clipboard write success on first stage.” |
| 21:04:19.336 | A separate AppsFlyer impression request is sent. |
| 21:04:19.971 | A same-origin request carries _fbp and fbp_auto_set, confirming client-side creation. |
Cookie implementation
The code treats Meta cookie names and AppsFlyer query names differently: cookies use leading underscores, while redirect parameters do not.
_fbp fallback
On a Meta-targeted click, the page checks for _fbp. If missing, it generates a value in Meta’s browser-ID shape and writes it for 90 days at Path=/.
It also writes fbp_auto_set=true. The HAR proves that this branch ran.
_fbc from click ID
The page reads fbclid from the landing query. It only synthesizes _fbc when that value exists and an _fbc cookie does not.
No fbclid existed here, so neither _fbc nor fbc_auto_set was created.
Meta event path
The page is tagged, but tagging and successful delivery are different findings. This capture only supports the former.
Pixel configured
Pixel ID 467581009113723 is embedded in the captured page config.
Init queued
The client calls the local fbq stub with a hashed external identifier.
Events gated
PageView and Lead are only called when fbclid is non-null.
Delivery fails
No library load completes and no Meta event beacon reaches the network.
Observed result
No Meta browser event was delivered. The pixel initialization may have remained queued locally, while PageView and Lead were skipped because this URL had no fbclid.
What AppsFlyer received
The click is attributed as Facebook-origin traffic, but it lacks the Meta browser and click identifiers that would make the attribution chain more specific.
Present
pid=facebook_w2a- Generic campaign, channel, ad, and ad-set placeholders
deep_link_value=genericDance- Browser user-agent
- A 64-character hashed
external_id - AppsFlyer smart-script fields
Absent
fbclidfbpfbc
AppsFlyer returns HTTP 301 to the Apple App Store and receives a separate impression request without these identifiers.
First-party event observed
The related call to data.aivideoart.co/api/customEventPush is operational telemetry, not proof of a Meta Pixel conversion.
The payload contains an event ID ending in -error, the original landing URL, a redacted hashed external identifier, the browser user-agent, and an item description saying “Clipboard write success on first stage” with the generated OneLink.
It contains no event_name, fbp, fbc, or fbclid.
Implementation defect
The capture and referenced code together point to a client-side sequencing issue.
The identifier is created too late
The OneLink is constructed during page initialization using the cookies available then. The fallback _fbp is created later in the click handler, but the already-built URL is not regenerated before navigation. Result: the site creates _fbp, yet the outbound AppsFlyer click does not receive it.
Channel roster beyond Meta
The same bridge page is configured for five paid web-to-app channels, each with its own click-identifier passthrough. Meta is one lane of five, not the whole funnel.
Configured channels
facebook_w2a— passesfbc,fbptiktok_w2a— passesttclid,ttpsnapchat_w2a— passesScCidpinterest_w2a— passesepiknewsbreak_w2a— passesnb_cid
Every channel additionally forwards external_id and browser_user_agent for server-side (CAPI-style) matching. target=google also resolves.
Naming and templates
Campaign parameters follow a fixed pattern per channel: <channel>_w2a-campaign, -channel, -ad, -adset.
Two OneLink templates are referenced from the page: 0DoU/8q4o34ah (the one in the capture) and 0DoU/r2ls2sbz.
Creative-to-feature routing
The deep_link_value parameter is the creative identifier, carried from ad click through the install gap into the app.
How it routes
The captured value genericDance matches the Ad Library creative (“Make anyone dance with AI Video”). The bridge page accepts arbitrary feature values — aiVlogCategory, viralDances, trends and others all resolve — so each ad deep-links into the specific feature it advertises rather than a generic home screen.
Why the clipboard write matters
The telemetry line “Clipboard write success on first stage” is the deferred deep-link mechanism: the campaign token is copied before the App Store handoff and read by the app on first launch. It is what preserves creative-level attribution across an install gap where the store link drops parameters — the same gap that loses fbp in the flow analyzed above.
Cross-reference with the product teardown
Dance is both the lead acquisition creative and the largest single recipe class in the catalog (44 of 201 cards, plus 4 pet-dance cards). A separate sweep of api.aivideoart.co/features/<key>/model — which authorizes on the x-userid header alone — returned the exact backend recipe for all 201 cards; every dance card runs nano-banana image preparation into Kling motion control. Acquisition spend and production stack point at the same feature.
HAR exposure
The capture includes substantially more than this landing flow and should be handled as sensitive data.
Credential exposure risk
The roughly 700 MB HAR contains 1,586 entries, hundreds of credential-bearing headers, access-token query fields, and embedded request and response bodies from Google, iCloud, Slack, WhatsApp, Apple, and other services. Because the artifact was downloadable without authentication, the hosted copy should be removed and potentially exposed credentials revoked or rotated.