Iterable SMS Revenue Attribution: Getting campaignId Into the Purchase Event Without Reworking Your Pipeline

Iterable supports multiple attribution approaches. Email-based projects can rely on redirect-set browser cookies, while SMS attribution requires that campaignId be present on the purchase event sent back to Iterable, commonly propagated via link parameters. This post explains the mechanics behind both options, what usually causes “email revenue works, SMS revenue doesn’t,” and a low-impact fix that keeps Segment mappings and purchase schemas stable by normalizing link parameters into the existing attribution fields.