Search Console and GA4 handoff

Measure acquisition without sending customer PII to analytics.

PrepPort already has privacy-safe website hooks for page, CTA, UTM, form-success, and first-party anonymous events. This page shows exactly what to create in Google Search Console and GA4, and what must stay out of analytics payloads.

Open sitemapOpen robots.txtOpen portalCloseout checklist

Safe copy values

Use these when creating Google properties or verifying the domain.

Search Console

  • Domain property: prepportglobal.com
  • Sitemap URL: https://prepportglobal.com/sitemap.xml
  • Robots URL: https://prepportglobal.com/robots.txt
  • Canonical site: https://prepportglobal.com
  • WWW site: https://www.prepportglobal.com

GA4 and first-party events

  • GA4 field to collect: GA4_MEASUREMENT_ID
  • Website meta hook: prepport-ga4-measurement-id
  • First-party endpoint: https://api.prepportglobal.com/api/public/website-event
  • Review command: npm run website:events -- --write

Setup checklist

These are the remaining account-side actions. They require Google/Cloudflare access and should be completed by the owner or delegated admin.

1. Search Console

Create a domain property for prepportglobal.com. If Google gives a DNS TXT value, keep it out of chat and run scripts/configure-google-search-console-dns.mjs locally to dry-run, apply, and verify the Cloudflare TXT record, then submit /sitemap.xml.

2. GA4 stream

Create a GA4 web data stream for https://prepportglobal.com. Record the owner and Measurement ID. Do not paste account secrets or private access notes into chat.

3. Deploy ID

After privacy review, place the Measurement ID into the site configuration hook. Use SEARCH_CONSOLE_VERIFICATION_TXT=<Google TXT value> node scripts/configure-google-search-console-dns.mjs --json before --apply. Keep first-party website events enabled even before GA4 is connected.

Privacy-safe conversion events

These are the event names PrepPort can use for acquisition measurement without customer-sensitive payloads.

Quote and RFQ

  • rfq_submit
  • rfq_success
  • service_estimate_submit
  • service_estimate_success

Operations intake

  • qc_inspection_success
  • onboarding_success
  • asn_success
  • fulfillment_success

Support and chat

  • support_ticket_success
  • web_chat_success
  • quote_response_success
  • status_lookup_success

Do not send to analytics

Use anonymous first-party event IDs and coarse attribution only.

Never include

  • Email, phone, WhatsApp, name, company, address, customer token, API key, payment reference, receipt URL, product document, raw message text, or supplier private data.
  • Exact quote values, bank details, PayPal links, legal decisions, refund decisions, or customer-specific operational notes.

Allowed dimensions

  • Page path, CTA name, service category, language, UTM source/medium/campaign/content/term, quantity bucket, platform category, and anonymous session hash.
  • Use event counts and conversion rates to choose campaigns; use CRM Lite for identifiable lead follow-up.

After setup

Run the website event summary weekly, compare service-page traffic against RFQ/service/onboarding submissions, and keep paid campaigns small until form conversion is visible.

Open portal