FunnelFox Destination
FunnelFox quick info
FunnelFox is in beta, and accepts Track, Page, Identify, Group, and Alias calls. If you reference it in the Integrations object, call it “FunnelFox”.
FunnelFox allows you to sort your sales operations in just a few clicks. Integrate your sales tools to eliminate data silos, get accurate CRM data to make the right decisions and know when opportunities require attention.
This destination is maintained by FunnelFox. For any issues with the destination, contact the FunnelFox Support team.
This document is about a destination which is in beta
This means that the FunnelFox Destination is in active development, and some functionality may change before it becomes generally available.
Getting Started
- From the Segment web app, click Catalog.
- Search for “FunnelFox” in the Catalog, select it, and choose which of your sources to connect the destination to.
- Enter the “API Key” into your Segment Settings UI which you can find on your personal FunnelFox Homepage under Data Sources > Websites.
Page
If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:
analytics.page()
Page calls will be sent to FunnelFox as a Customer Action: pageview
.
Screen
If you’re not familiar with the Segment Specs, take a look to understand what the Screen method does. An example call would look like:
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
Screen calls will be sent to FunnelFox as a Customer Action
.
Identify
If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:
analytics.identify('userId123', {
email: 'john.doe@example.com'
});
Identify calls will be sent to FunnelFox as an New or Updated Customer
event.
Track
If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:
analytics.track('Clicked Login Button')
Track calls will be sent to FunnelFox as an Customer Action
event.
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true
. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false
.
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
API Key
On your personal homepage locate the website destination and click on it to find your personal API Key.
This page was last modified: 20 Oct 2020
Need support?
Questions? Problems? Need more info? Contact us, and we can help!