Before launch: check that leads and conversions reach the right place

1. Define a completed action

Choose a precise event: a successfully submitted inquiry, a confirmed order or another completed business action. A click on a submit button is not necessarily a completed submission. Decide which system is the operational source of truth and what evidence confirms that the action finished.

For lead generation, distinguish a form submission from a qualified lead and a sale. They belong at different stages of the business process. If you count every contact as a sale, the campaign report cannot explain where the funnel is losing potential customers.

2. Test the destination customers actually use

Open the intended landing page on desktop and mobile, including the language and campaign parameters used for the ad. Check validation messages, the confirmation state and the path after submission. A translated page or an embedded browser may expose a problem that does not appear on the default desktop page.

Use a permitted test record with recognizable test details, not someone else’s personal information. Where production testing creates a real inquiry or message, coordinate it with the receiving team first. Do not assume that a success animation means the server accepted the submission.

3. Verify the receiving system separately

Find the resulting entry in the intended CRM, inbox or order system. Match it to the test using its reference and time. If a workflow should notify an employee, verify that delivery separately from the record being saved. An accepted API request is not proof that every downstream step completed.

On a narrow screen, scroll the table sideways to compare.

4. Keep event receipt and attribution distinct

A platform can receive an event without attributing it to an ad. Attribution depends on the eligible interaction, configured window and reporting rules. Do not generate artificial ad clicks to make a test appear as a real conversion. Label the test and use the platform’s supported diagnostics.

When reports differ, compare event definitions, date ranges, time zones, attribution settings and reporting delays before declaring data missing. Do not add Google, Meta and TikTok conversion counts together as if they necessarily represent distinct customers. More than one system may credit the same business action.

5. Check privacy and deduplication

Collect and send only the data appropriate for the purpose, with the required permissions and applicable consent. A server-side integration is not a reason to ignore privacy requirements. Keep real customer details out of screenshots shared for troubleshooting.

If more than one integration can send the same action, check how duplicates are handled. Decide what happens when a customer reloads a confirmation page, retries a request or submits twice. The objective is an understandable record of completed actions, not the highest possible event count.

6. Keep a small acceptance record

Record the tested page, language, device, action, time and resulting reference. Note who checked the business record and the measurement destination. Repeat the relevant test after changes to forms, routing, integrations or confirmation pages.

• Destination and validation work on the intended device.
• The completed action creates the expected business record.
• Notifications reach the correct team where applicable.
• The intended measurement destination receives the event.
• Unresolved attribution or reporting limitations are documented.