Adtrend teamProp firm conversion tracking connects the website visit to a confirmed challenge purchase. Use GA4 to see how people move through the funnel and the order system to verify what they paid. Use the two together to catch missing orders, duplicate signals and confusing attribution.
Map every event to an action
Record who owns each event, what triggers it and where you check it. Use the source that can confirm the action.
- Programme viewed. Use the storefront to record a view of a specific programme page. Keep the programme ID stable if the name or URL changes.
- Checkout started. Send GA4
begin_checkoutwhen the buyer enters checkout. Confirm your platform integration uses the same definition. - Payment confirmed. Send GA4
purchasefor a confirmed paid order with itstransaction_id,value,currencyanditems. Use the same nonempty transaction ID for any retry of that order. - Refund recorded. Use the order system to send the applicable GA4
refundevent and original transaction ID. Include refunded items and quantities when available, and check full and partial refunds separately.
Inventory existing tags and partner integrations before adding one. If a checkout app and a server integration both send the same purchase, choose the sender you can verify and control. Google documents purchase deduplication using transaction IDs for web streams. Your order workflow should still prevent repeat sends, including repeated confirmations or retried notifications.
Keep campaign context across checkout
Use a consistent naming scheme for tagged campaign links. Review whether your checkout is on the same domain, a subdomain or a separate provider domain. If you control the Google tag on both domains, Google’s cross-domain setup uses the same measurement ID and passes session information through the linker parameter. Test the whole path, including redirects and payment returns. With an external checkout you cannot tag, use the provider’s supported integration and record what you can verify.
Keep names, email addresses, phone numbers, payment details and documents out of analytics parameters and page URLs that analytics collects. Check what happens when consent is declined. Use server-side measurement only with the permissions and consent that apply to that event.
Run four tests before trusting the numbers
- Declined payment. Checkout starts. The order remains unpaid and no purchase event is sent.
- Successful payment. One eligible order appears in checkout and one purchase with the expected ID, currency and value appears in analytics.
- Repeated confirmation. Refresh the receipt or replay the test notification. Verify the order still counts once and no provisioning action repeats.
- Refund. Issue a supported test refund, reconcile it with the original order and confirm the adjustment is reflected in your reporting workflow.
Use a test checkout and a test analytics destination if available. Check the event parameters in DebugView or Realtime. Then verify the paid-order and refund reports for the same IDs and time window. If Google Ads imports your events, check each action’s role in bidding. A checkout start and a purchase answer different questions.
Reconcile the order ledger with GA4
Start with a complete date range and consistent time zone. Count unique paid IDs in the ledger, remove test records, account for refunds separately and match the eligible records to GA4. Review unmatched order IDs with the team that owns checkout.
Checkout reports 40 paid orders. Four came from sessions that did not allow analytics. GA4 shows 34 unique paid IDs. Investigate the two missing eligible IDs first. For each, check consent, checkout domain, event status and transaction ID in the test evidence.
Keep processor settlement, recorded revenue and channel credit in separate reports. Payment timing, attribution windows and consent can make these totals diverge. A weekly reconciliation should name the cause of any gap you can explain and assign someone to investigate the rest. Use the resulting cost per first purchase in your prop firm marketing plan.
Sources
Need a second look at your setup? See Adtrend’s conversion tracking service.
