Skip to main content
Send supported customer journey events to your business’s Meta Pixel account. This is measurement, not a loyalty balance source or proof that a message was delivered.

​
Configure the connection

  1. Select the intended business in Perkstar → Integrations → Meta Pixel → Connect.
  2. Enter the Pixel ID and Conversions API token from the property or data source you control in Meta Events Manager.
  3. Save in the integration workspace. These are business-level settings inherited by its cards; do not paste a different business’s credentials into a card.
  4. A saved-secret hint means the secret is already stored. Leaving it untouched preserves it; entering a replacement deliberately updates it.

​
Check an event

Use a controlled test customer and a supported enrolment or loyalty journey with the required recorded marketing consent. Inspect the matching event in Meta Events Manager. The implementation requires both the identifier and secret, plus the applicable consent, before firing these events. A saved identifier alone is not a completed verification.

​
Troubleshooting and ownership

Check the correct business, identifier, saved secret and test customer’s consent. Provider reporting can differ from Perkstar transaction totals; attribution events are not the accounting record. Do not remove consent requirements to make a test appear. Keep secrets private and rotate them through the provider when necessary. Use the available workspace controls to remove the configuration when retiring it, then confirm with a controlled test that no new event is generated. See security and privacy.