Wishpond Destination
Wishpond quick info
Wishpond accepts Track, and Identify calls. If you reference it in the Integrations object, call it “Wishpond”.
Wishpond accepts data in cloud-mode from all source types, and can accept data in device-mode from Analytics.js sources.
This destination is maintained by Wishpond.
The Wishpond JavaScript (browser) Integration destination code is open source and on GitHub. Feel free to check it out.
Getting Started
Wishpond works with Segment’s client-side javascript library: Analytics.js.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “Wishpond” in the Catalog, select it, and choose which of your sources to connect the destination to.
- In the destination settings, enter your Merchant ID and Trackey Key from Wishpond’s “API Keys” dialog. These are also found in your Wishpond Account in the “API Keys” dropdown under your account name in the top right corner.
- Segment automatically initializes Wishpond’s Tracking Code with your Tracking Key and Merchant ID when it next loads Analytics.js.
When you enable Wishpond in Segment, your Wishpond account starts to receive data when you use identify
or track
methods.
Identify
When you identify
a user, we’ll pass that user’s information to Wishpond. Wishpond Tracking Code, method identify, will be triggered with the params used to identify.
For instance, when Segment identify
is called:
analytics.identify('1e810c197e', {
name: 'Jane Kim',
email: 'jane.kim@example.com'
});
Wishpond Tracker will be called with the following parameters:
Wishpond.Tracker.identify('1e810c197e', {
name: 'Jane Kim',
email: 'jane.kim@example.com'
});
A new lead will be created be in your ‘Wishpond Leads Database’. The lead will have the attributes: name ‘Jane Kim’, email ‘jane.kim@example.com’. To more details how Wishpond’s identify works visit Wishpond API Docs: #identify.
Track
When you track
an event, we will send that event to Wishpond. Wishpond Tracking Code, method track, will be triggered with the params used to track the event.
For instance, when Segment track
is called:
analytics.track('Signed Up', {
plan: 'Startup',
source: 'Analytics Academy'
});});
Wishpond Tracker will be called with the following parameters:
Wishpond.Tracker.track('Signed Up', {
plan: 'Startup',
source: 'Analytics Academy'
});
A new event will be added to the lead that the current session is tracking. The event title will be ‘Signed Up’, and it will have the properties: plan: ‘Startup’,source: ‘Analytics Academy’.
To more details how Wishpond’s identify works visit Wishpond API Docs: #track.
Troubleshooting/ FAQ
Destination is not working properly
Make sure you have copied the right keys from Wishpond’s “API Keys” dialog, this destination will need Merchant ID
and Tracking Key
.
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.
Supported Sources and Connection Modes
Before you start, make sure Wishpond supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Web | Mobile | Server | |
---|---|---|---|
📱 Device-mode | ✅ | ⬜️ | ⬜️ |
☁️ Cloud-mode | ✅ | ✅ | ✅ |
Segment offers an optional Device-based Connection Mode for Mobile data going to Wishpond, so that you can use Wishpond features that collect data directly from the mobile device. To do this, you must package the Segment-Wishpond mobile SDK with the Segment mobile library.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Merchant ID
To find your Merchant ID, log into Wishpond, click on your account name in the top right corner, and then on ‘API Keys’ in the dropdown menu.
Tracking Key
To find your Tracking Key, log into Wishpond, click on your account name in the top right corner, and then on ‘API Keys’ in the dropdown menu.
This page was last modified: 20 Oct 2020
Need support?
Questions? Problems? Need more info? Contact us, and we can help!