Your numbers in Share
Under Where it's live, each site shows its last 30 days: how many visitors saw your form, how many started a request and how many sent one. Only the numbers are kept, never who the visitors were.
Google Tag Manager events
If your site uses Google Tag Manager, your form tells it about each request with three events:
- elitereply_request_sent: a client sent you a request.
- elitereply_qualified_request: the request came back qualified while the client still had the page open.
- elitereply_call_booked: the client booked a call in the form, with Calendly or Cal.com.
Each event fires once per request. No names, emails or answers are included; each event carries a short code that is the same for one request, and whether the form was on the page or opened from a button.
Count qualified requests in Google Analytics and Google Ads
- In Google Tag Manager, add a trigger: Custom Event, with the event name elitereply_qualified_request.
- Add a Google Analytics: GA4 Event tag that fires on that trigger. Name the event qualified_request.
- Submit and publish your container.
- In Google Analytics, mark qualified_request as a key event. Google Ads can then import it and bid for qualified requests, not just form fills.
A request is often judged a few moments after it's sent. If the client has already closed the page, that request isn't counted as qualified on your site, though it still reaches you as usual.
Turning it off
In Share, under Measure results, turn off Send events to my site. Your sites stop receiving the events within a few minutes.