Docs
← Back to Docs
Last updated: 2026-07-09

Paid Search Conversion Events

InvyMate's landing site emits a small set of named lead-intent events for paid-search reporting.

Active events

  • paid_search_demo_request_page_view Trigger: visitor opens /demo. Google Ads optimization: Secondary or Deferred.
  • demo_request_submit Trigger: visitor lands on /demo/thank-you?submitted=1 after a successful demo request form submission. Google Ads optimization: Deferred for now / Primary later.
  • paid_search_google_sign_up_click Trigger: visitor presses the Google sign-up button on /sign-up and is redirected into the Google auth flow. Google Ads optimization: Secondary or Deferred.
  • paid_search_pricing_page_view Trigger: visitor opens /pricing-comparison. Google Ads optimization: Secondary.
  • paid_search_sign_up_page_view Trigger: visitor opens /sign-up. Google Ads optimization: Secondary.
  • trial_signup Trigger: successful trial account creation from the email signup flow on /sign-up. Google Ads optimization: Primary.

These events are sent through the existing Google tag setup to GA4 and Google Ads. If direct Google Ads conversion actions are configured, set these optional public env vars on the landing app:

  • NEXT_PUBLIC_GOOGLE_ADS_DEMO_REQUEST_PAGE_VIEW_LABEL
  • NEXT_PUBLIC_GOOGLE_ADS_DEMO_REQUEST_SUBMIT_LABEL
  • NEXT_PUBLIC_GOOGLE_ADS_PRICING_PAGE_VIEW_LABEL
  • NEXT_PUBLIC_GOOGLE_ADS_SIGN_UP_PAGE_VIEW_LABEL
  • NEXT_PUBLIC_GOOGLE_ADS_TRIAL_SIGNUP_LABEL

If a label env var is empty, the app still sends the named GA4 event, but it does not send a direct Google Ads conversion hit for that event.

Deployment checklist

For demo_request_submit direct Google Ads tracking:

  1. Create or identify a Google Ads website conversion action for the demo request submit event.
  2. Copy the conversion label for that action.
  3. Set NEXT_PUBLIC_GOOGLE_ADS_DEMO_REQUEST_SUBMIT_LABEL in the landing deployment environment.
  4. Redeploy the landing app.
  5. Confirm the browser log for demo_request_submit shows a non-empty adsLabel.

For Google sign-up CTA click tracking:

  1. Use the named GA4 event paid_search_google_sign_up_click in GA4.
  2. If you want that event available in Google Ads, import the GA4 event into Google Ads as a conversion action.

There are two valid ways to use these events in Google Ads:

  1. Direct Google Ads site-tag conversions. Use the NEXT_PUBLIC_GOOGLE_ADS_*_LABEL env vars so the site sends a dedicated Google Ads conversion hit.
  2. GA4-imported conversions. Keep the named GA4 events, mark the relevant events as conversions in GA4, and import them into Google Ads.

For demo_request_submit, current code is already sending the GA4 event. A direct Google Ads conversion only starts once NEXT_PUBLIC_GOOGLE_ADS_DEMO_REQUEST_SUBMIT_LABEL is configured.

Current scope

Current tracking covers pricing page view, sign-up page view, demo request page view, guarded redirect-based demo_request_submit on /demo/thank-you?submitted=1, paid_search_google_sign_up_click on Google CTA press, and trial_signup after successful email-based trial creation. Google-based workspace signup still does not emit trial_signup, because that flow leaves the landing app before a success callback is observable there.

Tally redirect note

For the demo submit conversion to fire, configure the Tally form to redirect to /demo/thank-you?submitted=1 after successful submission.

This guarded route-based approach avoids dependency on the embedded Tally postMessage runtime and reduces accidental conversion fires from direct visits to /demo/thank-you.

← WebhooksPlans & Pricing (Overview) →