(Version 1.0 Effective September 1, 2026)
This product description is published by Swiftly Systems, Inc. (“Swiftly”) and is incorporated by reference into the reseller, wholesale-channel, or distribution agreement (the “Channel Agreement”) between Swiftly and an authorized reseller (the “Reseller”). It describes the Promotion Analytics Solution (“Analytics”) as made available to the retailers the Reseller enrolls (each, a “Retailer”).
1. Overview
Promotion Analytics measures how well a Retailer’s promotions performed. Swiftly ingests the Retailer’s point-of-sale transaction log, its promotions or ad sales plan, its product catalog, and its loyalty or customer file, and produces a promotion effectiveness scorecard covering items promoted in the period.
Promotion Analytics may be licensed with or without SmartCreate; neither is a condition of the other. It is a separate product from the insights dashboard included with SmartCreate, which reports on circular content, composition, and delivery rather than on promotion performance.
2. Service components
Measurement
• Item-level scoring of promoted items for each ad period, including sales lift measured against the item’s own non-promotion weeks and added sales dollars over the period
• Basket effect, being the change in a household’s total weekly spend attributable to the promotion, enabled for Retailers at which sufficient loyalty data is present
• A letter grade summarizing the result for an item
• Additional measures that Swiftly may make available from time to time, described in the methodology notes for the applicable version
Benchmarks and comparisons
• Peer and category benchmarks comparing a Retailer’s results for an item, category, or offer type against Swiftly’s broader dataset
• Recommendations derived from those comparisons
• Benchmarks are built from Aggregate Data and Deidentified Data drawn from across Swiftly’s customer base, as described in Section 6 and in the Swiftly Security Overview. Each Retailer’s data forms part of that dataset, and no Retailer’s or store’s individual results are disclosed to any other customer.
Period reporting
• Items scored, typical lift, total added sales, and the distribution of grades
• Performance banded by discount depth
• A ranking of the strongest promotions by added sales, and a list of promotions that sold less while promoted
Delivery
• A dashboard or report for each banner, with an item-level export
• Methodology notes identifying the version used for each delivery
• Reporting produced on the cadence agreed with the Reseller for each Retailer, and in any event not less than once per ad period and once per calendar quarter
General
• Hosted by Swiftly in a cloud environment
• Updates included at no additional charge
• AI-enabled, and subject to the artificial intelligence terms of the Channel Agreement and the Swiftly Acceptable Use Policy
3. What Swiftly needs from each Retailer
Delivered to Swiftly’s SFTP endpoint or through an agreed integration:
• Transaction log. Itemized point-of-sale data for all stores and all shoppers, store, date, item, units, price paid, discount applied and, where present, the loyalty or household identifier associated with the transaction. Delivered daily, with twenty-four (24) months of history at onboarding to establish baselines.
• Promotions or ad sales plan. The promotional plan for each ad period, items, offer type, promotional price, discount depth, and start and end dates. Promotional prices may also be inferred from the transaction log given a long enough history.
• Product catalog. Item master with descriptions, brand, size, and category hierarchy.
• Loyalty or customer file. The Retailer’s loyalty or customer records, sufficient to group transactions into households, refreshed at least monthly. Section 4 describes the ways this data can reach Swiftly.
• Store list and calendar. Store identifiers and addresses, and the Retailer’s ad week and promotion cycle calendar.
Analytics quality depends on the completeness of these feeds. Promotions that do not appear in the promotions feed, including digital coupons, loyalty-point offers, and unadvertised in-store specials, may not be detected, and items with too few non-promotion weeks may not be gradeable.
4. Getting a Retailer’s data to Swiftly
Pre-built integrations. Swiftly maintains pre-built integrations with loyalty and data providers including AppCard, Loyalty Lane, and Inmar. Where one of these can be reused for a Retailer, Swiftly charges nothing to onboard that Retailer’s data. Swiftly adds providers from time to time and publishes the current list on this page.
Direct file delivery. A Retailer may instead deliver its data to Swiftly directly, in a standard file format Swiftly supports. Swiftly ingests data delivered that way at no charge.
New integrations. Where a Retailer’s systems require an integration Swiftly has not built before, Swiftly quotes the estimated hours in advance and the work proceeds under a statement of work at the professional services rate in the applicable Services Schedule.
Third-party provider charges. A loyalty or data provider may charge its own fee to transmit a Retailer’s data to Swiftly. That fee is the provider’s, not Swiftly’s. Depending on the provider, it is billed to the Retailer directly or charged to Swiftly and passed through at cost, without markup, under the applicable Services Schedule.
5. Personal information
Promotion Analytics processes personal information. The Swiftly Data Processing Addendum at swiftly.com/legal/dpa applies to it, and Swiftly complies with that addendum for this Solution. A stable pseudonymous household or loyalty identifier is sufficient for all reporting described above, and direct identifiers may be hashed or tokenized before transmission. The prohibited data categories in the Data Processing Addendum and the Swiftly Security Overview apply.
6. Aggregate and Deidentified Data
“Aggregate Data” and “Deidentified Data” have the meanings given in the Swiftly Security Overview at swiftly.com/trust/security and the Swiftly Data Processing Addendum at swiftly.com/legal/dpa. Swiftly creates Aggregate Data and Deidentified Data from the data supplied for Promotion Analytics and uses it to build and maintain the baselines, benchmarks, peer and category comparisons, models, and recommendations described in Section 2, and to operate, support, secure, improve, and develop its products and services.
Swiftly does not identify any Reseller, Retailer, or store as the source of Aggregate Data or Deidentified Data, does not disclose any Retailer’s or store’s individual results to another customer, and does not attempt to reidentify any individual. Swiftly’s rights in Aggregate Data and Deidentified Data, and in the baselines, benchmarks, models, and reporting derived from them, are perpetual and are not affected by the end of a Retailer’s enrollment or by the return or deletion of that Retailer’s data.
7. Nature of Analytics Output
Analytics Output consists of modeled estimates produced from the data supplied. It is not audited financial information, and dollar figures reported are revenue rather than margin. Results depend on the completeness of the feeds and on assumptions and methodology that Swiftly documents and may refine from time to time, so figures produced under different methodology versions may not be directly comparable. Swiftly identifies the methodology version with each delivery and makes its methodology notes available.
Analytics Output is provided for internal business use, is not advice, and should not be the sole basis for any merchandising, pricing, or financial decision. It may not be used to make any decision about an individual, or to identify or target any individual shopper.
8. Support
Support tiers, severity levels, and response commitments for Promotion Analytics are set out in the Swiftly Service Level and Support Policy at swiftly.com/legal/support. Because Promotion Analytics is delivered as periodic reporting rather than as an interactive service, the reporting cadence in the applicable Services Schedule applies in place of the availability commitment in that policy.
9. Changes to this description
Swiftly may update this description from time to time and will give the Reseller at least thirty (30) days’ written notice before a change takes effect. Swiftly will not make a change that materially reduces the Services during the then-current term without the Reseller’s written consent. Swiftly will keep the version in effect on the date of a Channel Agreement, and each later version, available to the Reseller on request.