Send your event data from RudderStack to ConvertFlow.
4 minute read
ConvertFlow is an all-in-one platform that enables you to drive your conversions. It lets you create and deliver personalized user experiences via forms, quizzes, surveys, landing pages, and more.
RudderStack supports ConvertFlow as a destination where you can seamlessly send your event data.
In the web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the ConvertFlow native SDK from the https://js.convertflow.co/ domain.
Based on your website’s content security policy, you might need to allowlist this domain to load the ConvertFlow SDK successfully.
Get started
Once you have confirmed that the source platform supports sending events to ConvertFlow, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select ConvertFlow.
Assign a name to the destination and click Continue.
Connection settings
To successfully configure ConvertFlow as a destination, you will need to configure the following settings:
Website ID: Enter your ConvertFlow website ID.
For more information on obtaining your ConvertFlow website ID, refer to the FAQ section below.
Toggle on to send data through callback: Enable this setting to allow RudderStack to automatically record your ConvertFlow CTA interactions as track events.
List of Events: If Toggle on to send data through callback setting is enabled, enter the list of CTA interactions for RudderStack to track.
Map your events with ConvertFlow Standard Events: Use this setting to map the standard ConvertFlow events with custom event names.
For more information on this setting, refer to the Mapping events section below.
Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to ConvertFlow.
The following table lists the mappings between the RudderStack and ConvertFlow properties:
RudderStack property
ConvertFlow property
Data type
Presence
traits.email / context.traits.email
email
String
Required
Track
If you enable the Toggle on to send data through callback dashboard setting, RudderStack records the ConvertFlow CTA interactions and sends them as track events. You can then view and analyze these events in the other tools (connected to the same source in RudderStack).
RudderStack only tracks the CTA interactions specified in the List of Events field in the dashboard settings. If this setting is not specified, RudderStack tracks all below CTA interactions.
You can also update the standard ConvertFlow CTA events with custom event names by enabling the Map your events with ConvertFlow Standard Events setting in the RudderStack dashboard and specifying the required mapping:
Based on the mappings set in the above image, RudderStack replaces the standard event names "CTA Viewed" and "CTA Converted"with "Viewing CTA" and "Converting CTA" respectively.
FAQ
Where can I find the ConvertFlow website ID?
To get your ConvertFlow website ID, follow these steps:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.