Segment Connector

Fueled's Segment integration is available to BigCommerce merchants on our "Fueled Plus" plan and above.

Introduction

Segment is an enterprise Customer Data Platform. Segment is an ideal customer data pipeline/infrastructure solution for BigCommerce merchants facing the following challenges:

• Event tracking needs that span eCommerce storefronts, mobile apps, and custom software systems.

• Complex identity resolution requirements.

• Complex integration needs that require transforming data between systems.

Segment provides javascript libraries and APIs that can be implemented directly into your Shopify store. However, implementing Segment directly can take a lot of time and requires significant expertise. In fact, we originally designed Fueled to address these challenges — after years of manually implementing Segment for Shopify and BigCommerce merchants as consultants.

Fueled takes all of the hard work and time out of implementing Segment for Shopify. With Fueled, you can be up and running with Segment on BigCommerce in just one business day, rather than weeks.

Getting Started

Fueled's Segment integration leverages a server-side connection to Segment's APIs, via a Node.js connection. To get started, log into Segment and create a Node.js Source:

Fueled leverages a "Node.js" Source connection from Segment's Connector Catalog.

Give the Node.js Connector a meaningful name:

Name your Node.js connector

Copy the API Writekey for the Connector:

Copy the Node.js Connector Writekey.

Now, send this Writekey over to our team using OneTimeSecret.com or another secure mechanism, and we'll get your BigCommerce store sending events to Segment right away!

Our Segment eCommerce Event Specifications

Fueled supports Segment Page, Track, and Identify events:

Page Events

Page events tract a page load on a website. They automagically pull in basic UTM and campaign data. They can be extended to support additional event properties. An example can be found below:

analytics.page({
  path: '/products/sample',
  referrer: '<https://www.example.com/products/sample?variant=123456789>',
  search: '?variant=123456789',
  title: 'Example Product',
  url: '<https://www.example.com/products/sample?variant=123456789>'
});

Track Events

Track events fire when a user takes a specific action. Custom event types and properties can be defined for specific use cases. Standardized event types have also been defined for general use cases, as described below:

pageSegment Event Specifications

Identify Events

Identify events identify a website or application user, generally by a userId or an email address. When an identify event fires as part of a session that contains Track and Page events associated with a single, anonymous user, all of the events in this session are automatically associated with the identified user. With an Identify event, additional user/customer attributes can be defined and assigned. An example can be found below:

analytics.identify("12345abcd78910", {
  name: "Peter Parker",
  email: "[[e-mail]](<mailto:[e-mail]>)",
  address: {
    street: "7th St",
    city: "Queens",
    state: "NY",
    postalCode: "12345",
    country: "USA"
  },
  allOrderIds: "20,67"
});

Advanced Solutions

Custom Client-Side Events

Fueled supports custom client-side track events. If you need to track additional types of client-side events, you can simply leverage Fueled's client-side javascript library and these events will flow into Segment.

Modifying Event Payloads In Segment

Sometimes, merchants seek to modify the event payloads that Fueled sends to Segment as part of its standard eCommerce specification. To do so, you can use a combination of a Webhook Destination and a Source Function in Segment.

If you have questions about this approach, please contact [e-mail].