Formsable supports sending attributed Purchases to Google Analytics from any source, such as a sending a closed won CRM deal, a successful Stripe Invoice payment or an e-commerce purchase that has been successfully paid.
The first step is to locate the Google Analytics tracking id for the property you’d like to use for reporting.
Open Google Analytics, Admin – Property Settings page. Tracking Id should be the first item on the list. Record it.
After completing general Formsable setup, open ‘API Credentials’ tab. Select ‘Google Analytics’ service and enter Tracking Id in the Access Token field. Leave Refresh Token blank and enter arbitrary name you’d like to use as a reference (for example, corresponding Google Analytics property name). Press ‘Save’.
Open ‘Outbound’ tab. Select the Google Analytics Credential you’ve just saved and ‘Purchase’ event type. Press ‘Save’.
At this point required integration setup is complete and Formsable will start sending all Purchases that it attributed to Google Analytics visitors to Google Analytics Measurement API. Conversions will appear in all standard reports; additionally, Purchases will appear in the Conversions tab of E-commerce reports.
In addition to sending attribution details such as UTM parameters, referrer URL and landing page URL to Scoro, Formsable supports retrieving successful quotes from Scoro, attributing them to website visitors that produced leads and sending Purchase conversions to marketing APIs such as Google Analytics, Facebook Ads Conversion API and Google Ads API.
Formsable attributes Opportunities Closed Won in Salesforce to the original website visitors that generated the lead and sends successful conversion events to Google Analytics and ad platforms such as Facebook Ads and Google Ads.
Adding a server-side integration for tracking and attributing Clickfunnels purchases eliminates missing purchases from Google Analytics, Facebook Ads and Google Ads report, helping to have a precise picture of what campaigns and segments convert.
Events can be sent to Formsable from custom apps using its inbound webhook. This is convenient to attribute purchases and other conversions that aren't necessarily reflected in the payment system. For example, when the service usage accumulates before being invoiced once a payment threshold is reached or next billing cycle occurs.