Before a local service business changes its tracking, review offline conversion feedback: as an implementation brief

A useful implementation brief names the source, the destination, the identifier, and the failure response. That keeps a local service business from leaving important decisions inside a chat thread.

Read the symptom

The handoff depends on a business record being connected to the original ad interaction. The identifier, conversion action, timestamp, timezone, and sales status need to stay together while the deal moves through the CRM.

Inspect the path

• Find the identifier captured at the first interaction.
• Compare the CRM status with the conversion action name.
• Check the timestamp and timezone used by the upload.
• Keep a response log for accepted, rejected, and unmatched rows.

Write the brief

Make the upload record readable to someone who did not build the integration. For platform details, compare the fields in your implementation with Google’s offline conversion documentation.

If the next step is a shared source and outcome record, see LeadSheet.