Ryze Automation RouterInstall

Summary

Route input transaction data either to TrafficPoint pixels for immediate processing or upload aggregated CSV files to AWS S3 for monthly batch processing, based on the selected execution mode.

Inputs

• Script ID (required) — Unique identifier of your scraper script to associate with routed data.
• Main IO ID (required) — Primary brand IO ID used for handling translated data during monthly uploads.
• Execution Mode (required) — Determines routing behavior: Auto-detect based on trigger, force regular run (send to TrafficPoint), or force monthly run (upload to S3).
• Options — Collection of optional settings including Dry Run mode (test without sending data), Translator Node Name (for monthly uploads), Skip Deduplication (send all items without duplicate check), S3 Bucket Name for uploads, Verbose Logging, MySQL database names for scraper tokens and brand lookups.

Output shape

a single output item containing a JSON summary object with execution details

Output varies by execution mode: for regular execution, includes counts of sent, succeeded, failed, and inserted transactions; for monthly execution, includes metadata on uploaded CSV files, upload durations, and summary statistics. In Dry Run mode, reports what would have been sent or uploaded without actual data transmission.

Examples

Example 1: Force Regular Run with dryRun disabled

Sends non-duplicate transactions to TrafficPoint pixel API, stores successful sends in MySQL scraper_tokens table, and returns detailed metrics.

Example 2: Force Monthly Run with dryRun enabled

Processes input data into CSV files grouped by brand IO ID and translated data, reports estimated upload paths and sizes without uploading files to S3.