Sources and SDKs

Client-side libraries

Server-side libraries

Note: Server-side ingestion allows you to send data to MetaRouter directly from your application's server. We recommend using these sources only when client sources will not work, as client sources generally pass additional data about the user's browser and environment. Use cases will include payment events, data that needs to be calculated from a database query, or sensitive information.

Data Routing

We route all inbound data and translate it into a format that your destination of choice understands. You can see the sources that we currently support in the sidebar on the left hand side of the screen. If you don't see a source that you would like supported, send us an email at to request.

Source/Destination Compatibility Matrix

Check out the matrix below if you're wondering which sources are compatible with which destinations.

Client Server Mobile
Acquisio x x
Adobe Analytics x x
Amazon Kinesis
Amazon Redshift
Attribution x
Bloom Reach x x
Braze x
Calq x
Clicky x x
Criteo x x
DoubleClick x x
Drift x x
Facebook App Events x
Facebook Pixel x x
Google AdWords x
Google Analytics
Google BigQuery
Google Tag Manager x x
Heap Analytics
Kenshoo x x
Lucky Orange x x
Microsoft Ads x x
Netmining x x
Optimizely x x
OutBrain x x
Pebble Post x x
Resonate x x
Retention Science x x
Rubicon x x
S3 Event Logs
Taboola x x
Twitter Ads x x
VWO x x

© 2020 MetaRouter

Disclaimer: MetaRouter Cloud leverages code from several of Segment's fabulous library of open-source tools, including their source SDKs, destinations, and core Analytics.js library. As some of the core configurations outlined in our docs are largely identical to Segment's, we often re-purpose, and in some cases copy, directly from Segment's docs. In the cases where we have forked Segment's tools, we acknowledge and attribute all credit to Segment for their creation and subsequent documentation.