tracking-sync

To sync an approved GA4 event schema to your GTM workspace, you need a validated <artifact-dir>/event-schema.json file and a GA4 measurement ID. The process generates a <artifact-dir>/gtm-config.json file and pushes it to your chosen GTM targets via the official GTM API.

Yes, GTM sync requires interactive OAuth authentication with TTY enabled. This ensures secure authorization when connecting to your GTM account, container, and workspace, preventing automated or unauthorized access to your tracking configuration.

To prevent unapproved GA4 tracking plans from syncing to GTM, the workflow enforces schema-approval checks before execution. It blocks the sync unless the schema is explicitly approved or forced, treating custom dimensions as blocking items to ensure data integrity.

Yes, you can generate GTM configuration artifacts for Shopify tracking. The sync process supports Shopify-specific tracking artifacts, producing the necessary <artifact-dir>/gtm-config.json and accompanying workflow state files for your e-commerce event schema.

GTM sync requires interactive workspace selection to act as a guardrail against accidental deployment. It prevents the tool from auto-selecting GTM account, container, or workspace targets, ensuring you explicitly verify the destination before pushing live tracking configurations.

After syncing GA4 events to GTM, the process generates three primary files: <artifact-dir>/gtm-config.json, <artifact-dir>/gtm-context.json, and <artifact-dir>/workflow-state.json. These files capture the configuration, context, and current workflow status respectively.