Ryze Pixel SenderInstall

Summary

Deduplicates incoming affiliate events by transaction ID, checks them against MySQL, sends new or changed events to the TrafficPoint pixel endpoint, and records successful sends in MySQL. Provide the required event fields, a MySQL credential, TrafficPoint cookie header, script ID, and pixel URL; optional settings control dry runs, deduplication, logging, and payload output.

Inputs

• scriptId (required) — Scraper script ID included in the generated event data and execution summary; defaults to 3000.
• cookieHeader (required) — Full cookie header used to authenticate requests to TrafficPoint.
• pixelUrl (required) — TrafficPoint pixel endpoint; defaults to https://pixel.trafficpointltd.com/scraper.
• MySQL credential (required) — mySqlApi credential providing host, port, user, and password for the scraper_tokens table.
• Input item fields (required) — Each item must contain date, event, trx_id, and io_id. The operation also reads token, commission_amount, amount, currency, and parent_api_call; token defaults to an empty string. Transaction IDs are deduplicated case-insensitively within the input, keeping the last item for each ID.
• options.dryRun — Checks MySQL duplicates and reports items it would send, without sending pixel requests or writing to MySQL.
• options.skipDedup — Skips the MySQL duplicate lookup. Items are treated as new and successful sends are not recorded in MySQL.
• options.database — MySQL database containing scraper_tokens; defaults to cms.
• options.verbose — Enables detailed execution logging.
• options.includePayloads — Adds the generated pixel request payloads to the output for debugging.

Output shape

A single output item containing an execution summary and event details.

The summary reports input, new, duplicate, updated, send, and database counts as applicable. Exact duplicates are skipped when MySQL deduplication is enabled; records with changed amount or parent API call are resent. Successful pixel sends are inserted or updated in MySQL when deduplication is enabled. Sent item details are capped at 200, with total and truncation fields; failed sends and optional payloads are also included. Dry runs include a would-send count. Execution errors are thrown as a NodeOperationError with a JSON error summary.

Links

• n8n community nodes installation guide