RupayDeveloper docsOpenAPI specification

Google Analytics checkout tracking

Track live Rupay checkouts in your own Google Analytics 4 (GA4) property. Rupay's own analytics remains enabled.

Set up your Measurement ID

  1. In GA4, select the property used by your website.
  2. Open Admin → Data collection and modification → Data streams → your website's Web stream.
  3. Copy the Measurement ID, beginning with G- (for example, G-ABC1234567). Use the same ID as your website.
  4. In Rupay, open Checkout design → Google Analytics, paste the ID, and click Save analytics. Leave the field blank and save to disable merchant tracking.

Add Rupay to your domains

  1. In the same GA4 Web stream, open Google tag → Configure tag settings → Configure your domains.
  2. Click Add condition, choose Exactly matches, and enter rupay.dev.
  3. Add your website's domain as another condition, including each hostname used in the checkout journey (for example, example.com and www.example.com).
  4. Click Save. Enter domain names only, without https:// or a path.

Your website and Rupay checkout must use the same Measurement ID. Domain configuration alone does not guarantee a continuous session: Google's cross-domain linker must also survive your checkout navigation and redirects.

See Google's cross-domain setup and verification guide.

Verify tracking

After saving, open a live hosted checkout and check GA4 → Reports → Realtime for page_view and begin_checkout. Payment interactions can send add_payment_info; a confirmed successful payment sends purchase. Do not make a payment solely to test this setup.

Only live checkouts send merchant GA4 events. Settings apply to the selected merchant environment; staging checkouts do not send events even if an ID is saved.

Event data and reporting

Purchase events include currency, amount, items, and the checkout session ID as the transaction ID. Customer email, phone, raw visitor IP, and user-agent data are not attached to events. Checkout URLs are reduced to /checkout, and referrers are omitted to keep tokens and customer query parameters out of event data.

Disable enhanced measurement features that automatically inspect checkout interactions, especially form interaction tracking, in your GA4 Web stream. Rupay sends explicit ecommerce events.

Browser blockers, closing the checkout tab, and network failures can affect reporting. Use Rupay payment records as the source of truth for completed payments.