MyAlerts

File Requirements

General guidelines for working with feeds.

Why feeds?

MyAlerts offers two ways to populate data: Parsing and Feeds. While Parsing offers the easiest initial setup for your development team, Feeds offers greater power and flexibility, leveraging the full extent of MyAlerts capabilities. Feeds gives you control over the quality of your data as well as more precision with the timing, content, and quality of alerts. This translates into increased reliability, higher click-through rates, and better quality data available for reporting.

How does it work?

Your team uploads a data file matching our file requirements and specific feed type requirements, at a timing of your choice. The MyAlerts Feeds system consumes the data and converts it into relational schema used to power your alerts and reporting. As new user intent flows in, we combine this data with your feed data in realtime, accurately alerting users when relevant information matches intent.

What types of feeds are available?

File Requirements

Delivery Method
  • Via port 44422
  • Via port 22 (requires whitelisting)
  • MyAlerts will provide credentials
Character Encoding

All special characters must be properly encoded

File Formats

Data

.csv or .txt containing header and delimited row data

Encryption

.gpg

Compression

gz

Data Format

Column Headers

Case-insensitive.

Row Data

  • Must have consistent column order
  • Cannot reference another row
  • Case-insensitive
Delimiters

Tab (recommended)

Headers required on first row

CSV

  • Headers required on first row
  • Follows standard CSV rules for special characters and encoding

MD5 Hash

To verify your feed uploads and processes correctly, upload an md5sum along side your feed file. i.e. If your feed file is named myfeedfile-20170101.gz, also upload myfeedfile-20170101.md5 to the same location.

Updated about 13 hours ago

File Requirements


General guidelines for working with feeds.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.