RudderStack supports Mouseflow as a destination where you can send your event data seamlessly.
RudderStack supports sending event data to Mouseflow via the following connection modes:
Once you have confirmed that the source platform supports sending events to Mouseflow, follow these steps:
RudderStack sends the page-related information like the path or the page URL to Mouseflow using the Adding a virtual pageview%3B-,Adding%20a%20virtual%20pageview,-_mfq.push) method:
You can customize the page-related details sent to Mouseflow by passing the values in the properties.path field. RudderStack then maps these details to the _virtualPath parameter before sending them to Mouseflow, as highlighted in the below table:
properties.path / context.path
The following snippet highlights how RudderStack sends the data in the sample page call above to Mouseflow:
Setting custom variables via the integrations object
RudderStack enables you to send custom variables to Mouseflow via the identify and track calls by passing them via the integrations object.
A sample identify call highlighting this feature is shown below:
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
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.
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.