Audience Stream API vs SFTP

[marcjp]

Hi,

I am scheduling an API call to pass data to either the audience stream API or SFTP. I was wondering what they pros and cons of each are and which would be the best solution?

Thanks in advance!

[dan_george · Accepted solution]

@marcjp

I believe you are referring to bringing data into the UDH either by Omnichannel (batch file process) or the Tealium Collect API (real-time endpoint). Correct?

If so, please see my comments below.

Omnichannel

• Pros
  • Preferred for data that does not need to be actioned against immediately
  • Great for systems that are not open to the public
  • Great for systems that are not able to trigger a request over HTTPS
  • Marketer friendly - meaning marketers can manually export data from systems and upload to FTP/SFTP/S3
  • Though can still be made programmatic
• Cons
  • Delayed enrichment to visitor
  • Supports only 1 million row imports per day
  • May be a manually effort

Tealium Collect API

• Pros
  • Always programmatic
  • Immediate enrichment to visitor
  • Can support heavy volume and his highly scalable
• Cons
  • Typically requires developer resources to setup and automate

All events feeding into the UDH effect your contract price. Please contact your Sales Representation or Account Manager to ensure you have sufficient volume so that you do not incur overages.

Please let me know if this helps answer your question.

Cheers,

-Dan

[marcjp]

Hi @dan_george,

Thankyou for your response!

I am looking at the pros and cons of using vdata pixel to bring data into the universal data hub, is this the same as the Tealium Collect API?

Thanks in advance!

[dan_george]

Hi @marcjp

Yes, part of the Tealium Collect API path is /vdata/ so they are the same.