Factual Engine

Mobile location enrichment

  • Analyzes location data and how it changes throughout the day to fuel user insights and segmentation

  • Correlates a device’s location to a unique place or point of interest

  • Creates targeting rules (Circumstances) based on user location combined with day of week, time of day and specific place attributes

  • Triggers emails, push notifications, or other actions based on the custom Circumstances rules

Factual Engine

How Factual Engine Works

Installing the Engine SDK in your app enables you to gather and analyze information about your users’ location. Engine caches the relevant portion of Factual’s Global Places data on the device to determine where the user is, beyond raw location. Engine needs device location data in order to work and will use whatever location permissions your app has authorized. You can also set custom rules to trigger “actions” like push notifications or emails.

Sharing the data and insight that Factual Engine collects with tools like analytics, marketing automation, and your data warehouse will require research and custom coding. A software engineer will need become familiar with Factual Engine’s API and webhooks. The API enables the data that Factual collects to be forwarded to external tools and webhooks allow you to hook into that data as it occurs and is tracked via Engine’s SDKs. The data that’s collected will need to be collected, re-formatted, and sent to each tool where you want the data.

View a user’s journey through known physical locations
View a user’s journey through known physical locations
Configure Circumstances that trigger messages or offers to users based on their location
Configure Circumstances that trigger messages or offers to users based on their location
Record a user’s specific location or nearby places
Record a user’s specific location or nearby places
Factual Engine

Get more out of Factual Engine with Segment

The Factual Engine Source is a cloud-based event source. You simply include, configure, and initialize the Engine SDK as you normally would, and then add only a few lines of code to trigger correctly formatted events to Segment in response to your dynamic triggers and actions. This  event data then flows seamlessly to your downstream Segment Destinations. Once the Factual Engine Source is enabled, any Segment Destination that can accept server-to-server data can accept data from Factual Engine. The data is also automatically streamed into your next warehouse sync. The data generated from the Factual Engine can also be easily combined with other Source data collected via Segment without any additional development work on your end.

Similar integrations

View all integrations

Integrate Factual Engine with Segment

Segment makes it easy to set up Factual Engine.