Conversion Reporting

Conversion Reporting closes the loop after Meta Lead Ads brings a lead into Whispyr. Once active, Whispyr reports the lead's CRM stage changes back to Meta so campaigns can optimize for quality, not only form fills.

Before you start

Make sure you have:

• A Whispyr admin account.
• Meta Lead Ads connected and live for the same Whispyr scope. Conversion Reporting depends on real Meta lead IDs from that integration.
• Access to the Meta Business account that owns the dataset.
• Permission to create or manage a Meta dataset and generate a dataset access token.
• The rights and consents needed to share lead conversion outcomes with Meta for advertising measurement.
• For the optional test event: at least one real Meta lead already received in this Whispyr scope.

What you will do

You will create or choose a Meta dataset, copy its dataset ID, generate a dataset access token, save both values in Whispyr, confirm the data-sharing acknowledgement, and optionally send a Meta Test Events check.

After activation, Whispyr sends the CRM funnel automatically. There is no status mapping screen to configure.

Step 1. Create or choose a Meta dataset

In Meta Business Settings, open Data sources → Datasets & pixels. If you do not already have the dataset you want to use for Whispyr, click Add.

Choose Create a new dataset, enter a clear name, and create it.

Meta confirms the dataset was created. Click through to Events Manager so you can copy the dataset details.

Step 2. Copy the dataset ID

In Meta Events Manager, select the dataset and open Settings. In the Details section, copy the Dataset ID.

The dataset ID is not a secret. Whispyr shows it in clear text later so admins can confirm the connected dataset.

Step 3. Generate a dataset access token

Stay on the dataset's Settings tab. In the direct integration area, click Generate access token.

After Meta generates the token, copy it.

Step 4. Save the dataset in Whispyr

In Whispyr, go to Settings → Integrations → Meta → Conversion Reporting.

Paste the dataset ID first.

Paste the dataset access token.

Click Save changes. Whispyr encrypts the access token at rest.

Step 5. Activate Conversion Reporting

After saving, Whispyr keeps the dataset pending until an admin confirms the data-sharing acknowledgement. Click Review & activate, read the prompt, and confirm only if your organization has the rights and consents needed to send these conversion outcomes to Meta.

When activation succeeds, the card shows Active. From this point forward, Whispyr can send production conversion events for this scope.

Step 6. Understand what Whispyr sends

Whispyr sends each CRM stage as the Meta event name. The current stage names are:

• New Lead
• Qualified
• Meeting Scheduled
• Meeting Completed
• Expression of Interest
• Reserved
• Done Deal
• Lost Lead
• Unqualified
• Future Contact
• Unreachable

For matching, Whispyr sends Meta's raw lead ID. Phone and email identifiers are hashed before sending. The Done Deal stage can also include value and currency when the closed deal has them.

Step 7. Optional: send a test event

Meta's Test events tool lets you check that the dataset and token are accepted.

In Meta Events Manager, open the dataset and go to Test events. Open the channel dropdown.

Choose Website.

Copy the generated test event code.

Back in Whispyr, paste the test event code and click Send test event.

Whispyr sends the test against one of this scope's real Meta leads. If no real Meta lead has arrived yet, Whispyr will show an awaiting-first-lead message instead. Do not make up a lead ID; Meta rejects synthetic lead IDs for this flow.

Test events still flow into Meta measurement. Sending one is optional and does not activate Conversion Reporting.

Step 8. Monitor recent emissions

After activation, use Recent emissions on the same Whispyr card to see production sends, skips, and failures for the scope.

• Sent means Meta accepted the event.
• Skipped: no lead ID means Whispyr did not have a Meta lead ID to match.
• Skipped: duplicate means the same milestone was already sent for that Meta lead.
• Failed means Meta rejected the event or the request failed. Retryable rows show a Retry button.

If Meta rejects the access token, Whispyr pauses the connection and marks it Needs reconnect. Generate a fresh dataset access token in Meta, edit the Whispyr card, and save the new token.

Troubleshooting

Whispyr says to set up Meta Lead Ads first

Conversion Reporting depends on the Meta lead IDs captured by the Lead Ads integration. Finish the Meta Ads setup for the same scope, wait until it is live, then return to Conversion Reporting.

Whispyr says there is no testable lead yet

A test event needs a real Meta lead already received by Whispyr. Submit or wait for a real Meta lead in that scope, then send the test again.

Meta does not show the test event

Make sure the dataset ID, access token, and test event code all come from the same dataset. Keep Meta's Test events page open while sending the test from Whispyr.

The connection needs reconnect

Meta rejected the saved dataset access token. Generate a fresh token from the dataset's Settings tab, edit the Whispyr card, paste the new token, and save.

A production event was skipped

Open the row in Recent emissions and read the reason. The most common skips are missing Meta lead ID or a duplicate milestone that Whispyr already sent.

FAQ

Does this require Meta App Review?

No. Conversion Reporting uses a dataset access token from Events Manager. It is separate from the Meta Developer App setup used for inbound Lead Ads.

Is this separate from Meta Lead Ads?

Yes, but it depends on Meta Lead Ads being live for the same scope. Lead Ads brings the lead into Whispyr; Conversion Reporting sends later CRM outcomes back to Meta.

Does Whispyr send raw phone numbers or emails?

No. Phone and email identifiers are hashed before they are sent to Meta. Meta's lead ID is sent raw because Meta requires it for Conversion Leads matching.

Can I choose statuses or map events?

No. Whispyr sends the full CRM funnel automatically. The Meta event name is the CRM stage name.

Can I disconnect later?

Yes. Disconnecting stops new conversion events. The dataset, encrypted token, and consent history stay available so an admin can reactivate or reconnect later.