Meta Ads (formerly Facebook Ads) allows you to build powerful retargeting audiences based on real-world user actions. By integrating Uniqode with Meta Ads through the Insights tab, you can automatically send QR Code scan events to your Meta dataset — enabling you to reach people who have already engaged with your offline campaigns.
Prerequisites
Uniqode Business+ plan or above with admin privileges
At least one QR Code created in the platform
An active Meta Ads account with access to Events Manager
Insights enabled on your Uniqode account (start a free trial from the Insights section if not yet active)
Setting Up Meta Ads Retargeting
Step 1 — Navigate to Meta Ads in Insights
Sign in to your Uniqode account.
Click Insights in the left navigation menu.
If Insights is not yet active, click Start Free Trial to enable it before proceeding.
Inside the Insights tab, click the Meta Ads option.
If the integration is not yet connected, you will be prompted to connect it.
Step 2 — Understand the Two Credential Types
The Meta Ads integration supports two levels of tracking, each requiring different credentials:
Dataset ID only — Enables client-side tracking (browser/pixel level). Events are fired from the user's browser.
Dataset ID + Conversion API Access Token — Enables both client-side and server-side tracking. Server-side tracking fires events directly from Uniqode's servers to Meta, making it more reliable and less affected by ad blockers.
Both credentials are obtained from your Meta Ads account.
Step 3 — Find Your Dataset ID in Meta Ads
Log in to your Meta Ads account.
Navigate to Events Manager.
All available data sources (datasets) will be listed here.
Select the relevant dataset (e.g., the one associated with your Uniqode account or desired property).
Go to the Settings tab of that dataset.
Copy the Dataset ID shown there.
Step 4 — Paste the Dataset ID into Uniqode
Return to the Uniqode Insights → Meta Ads connection screen.
Paste the copied Dataset ID into the Dataset ID field.
This is the minimum required to establish a connection and enable client-side tracking.
Step 5 — Add the Conversion API Access Token (Optional but recommended)
To also enable server-side tracking:
In Meta Ads, go to Events Manager and open your dataset's settings.
Navigate to the Conversions API section and select Set up direct integration.
Select the Dataset ID for which you want to generate a token.
Click Generate Access Token.
Copy the generated token.
Back in Uniqode, paste it into the Conversion API Access Token field.
Step 6 — Configure Scan Events
After entering your credentials, you will see the Configure Scan Event screen. Define the custom event name to be passed to Meta when a QR Code scan occurs (for example, QR_Scan). You can use a test event name during setup to verify the connection.
Step 7 — Configure Identity Matching (Optional)
Toggle the Identity Matching option to control whether Uniqode sends the scanned user's email address alongside the event data passed to Meta.
Toggle OFF — Only the event data is sent; no email address is included.
Toggle ON — If Uniqode has collected an email address for the scanned user (e.g., via a Uniqode form), that email is included with the event, improving Meta's ability to match the event to a known user profile.
Step 8 — Validate and Save
Click Validate Connection.
The configuration is automatically saved when you proceed — no separate Save button is required.
After validation, the dashboard will reflect the active tracking mode:
Dataset ID only: Shows "Client Pixel Only" — browser-level tracking is active.
Dataset ID + Conversion API Token: Shows both client-side and server-side tracking as active.
Viewing Events in Meta's Dataset
To verify that events are being received on the Meta side:
Go to your Meta Ads account and open Events Manager.
Select your dataset and navigate to the Overview tab.
Note: Events can take approximately 30 minutes to appear in the Overview. If events are not immediately visible, this is expected behavior — wait a few minutes and refresh.
Troubleshooting
The Uniqode platform logs all events sent to Meta via server-side tracking. You can access this log from within the Insights → Meta Ads section to view a complete record of every dispatched event, including whether each event succeeded or failed. Use this log to diagnose dataset or tracking issues.
Note: Meta's "Test Events" feature is not currently supported through this integration. To verify your setup, use the standard event view in Events Manager and allow up to 30 minutes for data to propagate.