Meta Ads Tracking, Events and Privacy Set-Up Plan
Plan pixel or conversions set-up with consent in mind.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan tracking for Meta ads. Website and platform: [WEBSITE_PLATFORM]. Events to track (view content, lead, purchase): [EVENTS]. Consent and privacy approach: [CONSENT_APPROACH]. Existing set-up: [EXISTING_SETUP]. Table of events with name, trigger, parameters sent, value, and whether personal data is involved (it should not be). Explain deduplicating events when two methods (browser-based and server-based) report the same action [VERIFY], and how to implement and test them, with test steps in order and the evidence to keep. Describe the consent flow in words, including what happens when a visitor declines; tracking should follow user choices and local law, which differs by place and changes [VERIFY]. List data that should never be sent (sensitive personal data), minimise data, and involve the person responsible for data protection. Write a test log, a monthly reconciliation of reported leads to real leads with arithmetic and a tolerance, and a plan for when tracking breaks. Verify platform policies and settings before acting [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.