If your use case requires this data in Funnel, you can request it as a Custom Connector.
Custom Connectors and the Custom Connector Request feature are available in the following plans: Business and Enterprise. See our Pricing page for more details.
Reports
Mailings
Mailings Id
Mailings Name
Mailings Resource Type Id
Malings Adressees
Mailings Conversions
Mailings Conversion Sum
Mailings Conversion Sum Float
Mailngs Clicks
Mailings Click Rate Relative
Mailings Click Rate Multiple Relative
Mailngs Clicks Unique
Mailings Opening Rate
Mailings Opening Rate Por
Mailings Opening Rate Multiple
Mailings Bounce Rate
Mailings Campaign Id
Mailings Sendout Starttime
Mailings Sendout Endtime
Mailings Sendout Triggertime
Mailings Unsubscriptions
Mailings Targetgroup Id
Mailings Targetgroup Name
Mailings Splitcampaign Id
Mailings Splitcampaign Name
Profiles
Profiles Country
Profiles Permission
Profiles Deleted
Profiles Profileid
Profiles Kundengruppe
Profiles Change Date
Profiles Create Date
Tracking History
Tracking History Id
Tracking History Resource Id
Tracking History Resource Name
Tracking History Resource Type Id
Tracking History Sub Resource Id
Tracking History Sub Resource Name
Tracking History Sub Resource Type Id
Tracking History Sub Url
Tracking History Profile Id
Tracking History Type
Tracking History Timestamp
Tracking History Referrer Domain
How to Request this Custom Connector
To request Evalanche data, submit a Custom Connector Request (see link here for instructions) or select the Evalanche tile marked custom after enabling Show custom connectors. Selecting the tile automatically sends your request.
If you are interested in Evalanche data that hasn't been covered here, we would like to encourage you to connect with our Integration Engineering team by submitting a Custom Connector Request. They will be more than happy to explore the potential of obtaining additional data.
Notes on Custom Connector
Subscription Required: Access to the API is available through a paid customer subscription.
Domain-Based Data Access: Each customer’s data is restricted to their own domain for security and privacy.
Unique Customer ID: Every customer receives a unique ID that must be included in all API requests.
Data Safeguards: Mailing data is filtered by send date to ensure completeness and prevent data loss.