Campaign use cases
Routing Meta and Facebook Ad Traffic with Clear Boundaries
Meta placements mix app, in-app browser, and web contexts, so source preservation and mobile testing matter more than a single user-agent rule.
Trace placement-to-page journeys
Document how Facebook and Instagram placements open the campaign URL, including in-app browser steps and any tracker redirect. Use separate test notes for feed, story, and other materially different paths rather than assuming every click exposes identical context.
Choose resilient source evidence
Preserve explicit campaign parameters and compare them with referrer and browser context. Treat referrer absence as a condition to understand, not automatic suspicion, because application and privacy behavior may legitimately remove it.
Test destinations inside mobile environments
Check viewport layout, navigation, cookie behavior, redirects, and parameter retention in the actual in-app journey. A page that works in desktop Chrome can fail before the routing system receives a meaningful event on mobile.
Handle review-like visits conservatively
Some verification traffic may resemble ordinary sessions while some real people use restricted networks or browsers. Combine evidence, maintain a safe fallback, and avoid claims that the system can know a visitor's employment or exact purpose.
Compare sources after launch
Segment events by placement and campaign identifiers, then review unexpected destination ratios and repeated reasons. Re-run controlled visits whenever creative links, tracking settings, or the mobile landing experience changes.