Remerge event forwarding checks documented request fields.

Exact documented event and BI forwarding GET endpoint. Scoped warning checks preserve open identity applicability and metadata strings; regional creative and video callbacks are excluded.

What this pack matches

Hosts: remerge.events
Paths: /event
Vendor docs: help.remerge.io/hc/en-us/articles/6078711583260-Event-Data-Forwarding

Rules

Codes are stable. A finding in CI, MCP, or the playground lands on the same id.

Field	Required	What it checks	Rule ids	Source
`app_id`	required	Documented mandatory store app identifier. Preserve Android package names and iTunes identifiers without inferring a shared numeric grammar. Presence diagnostic severity: warning.	`vendor.remerge-event.param.app_id.missing`	docs
`event`	required	Documented mandatory event name. Examples do not close the event vocabulary. Presence diagnostic severity: warning.	`vendor.remerge-event.param.event.missing`	docs
`partner`	required	Documented mandatory tracking partner name; registration is external. Presence diagnostic severity: warning.	`vendor.remerge-event.param.partner.missing`	docs
`key`	required	Documented mandatory partner key issued by Remerge; no local issuance or acceptance check. Presence diagnostic severity: warning.	`vendor.remerge-event.param.key.missing`	docs
`ts`	optional	Optional event Unix epoch timestamp is documented as ten digits in UTC. No freshness window is inferred. Presence diagnostic severity: warning.	`vendor.remerge-event.param.ts.empty` `vendor.remerge-event.param.ts.invalid`	docs
`idfa`	optional	Optional local format advisory for the documented uppercase Apple IDFA. Cross-platform mandatory labels do not establish when this ID is applicable. Presence diagnostic severity: warning.	`vendor.remerge-event.param.idfa.empty` `vendor.remerge-event.param.idfa.invalid`	docs
`aaid`	optional	Optional local format advisory for the documented lowercase Android Advertising ID. No simultaneous Apple and Android ID requirement is inferred. Presence diagnostic severity: warning.	`vendor.remerge-event.param.aaid.empty` `vendor.remerge-event.param.aaid.invalid`	docs
`idfv`	optional	The vendor ID is described as applicable to iOS only. Applicability, alternatives and the mandatory table label require integration context. Presence diagnostic severity: warning.		docs
`data`	optional	The guide allows event metadata as JSON or a single string. No JSON-only syntax or custom-member schema is imposed. Presence diagnostic severity: warning.		docs
`non_app_event`	optional	Optional literal true or false. BI forwarding requires true when caller context establishes a non-app event; that context cannot be inferred from an event name. Presence diagnostic severity: warning.	`vendor.remerge-event.param.non_app_event.empty` `vendor.remerge-event.param.non_app_event.invalid`	docs
`country`	optional	Optional ISO alpha-2 country-code shape only. Registry membership and geographic truth are not checked. Presence diagnostic severity: warning.	`vendor.remerge-event.param.country.empty` `vendor.remerge-event.param.country.invalid`	docs
`currency`	optional	Optional advice for current or historical ISO 4217 assignment. Case is not restricted and no currency/value conversion or account configuration is inferred. Presence diagnostic severity: warning.	`vendor.remerge-event.param.currency.empty` `vendor.remerge-event.param.currency.invalid`	docs
`device_name`	optional	Optional Device name. Presence diagnostic severity: warning.		docs
`os_name`	optional	Optional OS name; android and ios are examples, not a closed enumeration. Presence diagnostic severity: warning.		docs
`os_version`	optional	Optional OS version. Presence diagnostic severity: warning.		docs
`app_version`	optional	Optional Application version. Presence diagnostic severity: warning.		docs
`user`	optional	Optional Customer user ID. Presence diagnostic severity: warning.		docs
`revenue`	optional	Optional monetary-number sanity advice. The guide documents monetary units but not the complete receiver lexer; signed, fractional, leading-zero and exponent forms remain accepted. No value conversion or relationship between the two carriers is inferred. Presence diagnostic severity: warning. Evidence: heuristic.	`vendor.remerge-event.param.revenue.empty` `vendor.remerge-event.param.revenue.invalid`	docs
`revenue_float`	optional	Optional monetary-number sanity advice. The guide documents monetary units but not the complete receiver lexer; signed, fractional, leading-zero and exponent forms remain accepted. No value conversion or relationship between the two carriers is inferred. Presence diagnostic severity: warning. Evidence: heuristic.	`vendor.remerge-event.param.revenue_float.empty` `vendor.remerge-event.param.revenue_float.invalid`	docs
`operator`	optional	Optional Mobile operator or carrier. Presence diagnostic severity: warning.		docs
`zipcode`	optional	Optional Regional postal code. Presence diagnostic severity: warning.		docs
`city`	optional	Optional City name; UN/LOCODE standardization is guidance. Presence diagnostic severity: warning.		docs
`country_subdivision`	optional	Optional State or subdivision name. Presence diagnostic severity: warning.		docs
`partner_device_id`	optional	Optional Partner user ID. Presence diagnostic severity: warning.		docs
`ip`	optional	Optional IPv4 or IPv6 literal syntax advice. Address ownership, forwarding provenance and collection acceptance remain external. Presence diagnostic severity: warning.	`vendor.remerge-event.param.ip.empty` `vendor.remerge-event.param.ip.invalid`	docs
`language`	optional	Optional Simple or extended language value; examples admit both hyphen and underscore. Presence diagnostic severity: warning.		docs
`sdk`	optional	Optional Client SDK version. Presence diagnostic severity: warning.		docs
`https_required`	recommended	Remerge documents HTTPS for event forwarding.	`vendor.remerge-event.https_required`	docs
`method`	required	The public event-forwarding interface documents GET. Complete HTTP capture contract. Presence diagnostic severity: warning.	`vendor.remerge-event.http.method.missing` `vendor.remerge-event.http.method.empty` `vendor.remerge-event.http.method.invalid`	docs

Validate a payload

pixellint validate url "$ARTIFACT" --rulepack vendor/remerge-event

Try this failing payload in the playground. An example with a validation finding.

https://remerge.events/event?event=synthetic&partner=synthetic-partner&key=synthetic-key

cargo install pixellint · npm install pixellint