PixelMe Destination

PixelMe Smart Attribution works by gathering all your traffic from any source and attributing it instantly using UTMs. Combined with our event tracking, you can easily see which traffic is causing which conversions on your website.

This destination is maintained by PixelMe. For any issues with the destination, please reach out to their team.

NOTE: The PixelMe Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on August 7, 2019. If you are interested in joining their beta program or have any feedback to help improve the PixelMe Destination and its documentation, please let their team know!

Getting Started

The first step is to make sure PixelMe supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “PixelMe” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can directly copy-paste from your PixelMe dashboard.
  4. To find the API Key, go to Settings > Integrations

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:

analytics.page()

Unique page calls will be sent to PixelMe as a Visitor.

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does. An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Screen calls are saved but not processed by default. If you want to use screen calls with PixelMe, please let their team know.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@segment.com'
});

Identify calls are saved but not processed at the moment. PixelMe will use these calls shortly to merge users path to attribute a conversion event to the correct anonymous id. Of course, all Identify calls received will be used to merge users, so PixelMe recommends to send them as soon as you can.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('SignUp')

Track calls will be sent to PixelMe as conversion events. In the previous example, a SignUp conversion event will be sent to PixelMe.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

API Key

You can find your API key inside Settings => Integrations

Adding PixelMe to the integrations object

To add PixelMe to the integrations JSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration:
  • PixelMe


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!