Skip to main content

Integrations

Open Settings → Apps & developers → Integrations as a project administrator and select Segment or Spoonity, when the project returns those sections.

Current catalog and example settings​

The project’s catalog controls which provider sections and fields appear. Review the intended provider account and project before editing.

Before you configure an integration​

  • Confirm that your organization has authorized the intended Dashboard and provider-account changes.
  • Collect the account-specific values through your approved secret-management process; do not use a value from another project, environment, screenshot, or ticket.
  • Identify the isolated test and the exact result to verify, such as a saved configuration, an approved test event, or a provider-owner confirmation.
  • Change one setting at a time. A successful Dashboard response is different from provider acceptance and downstream behavior.

Save behavior and partial persistence​

For ordinary integration fields, the current Dashboard source stages edits until Save and writes configuration records sequentially. A later failure can follow an earlier persisted change, so a multi-field save is not evidence that every identifier or enablement choice was stored. This describes the source contract only; no request, provider handoff, event, loyalty update, or analytics result is verified here.

Configure Segment​

Open Segment. Enter the tracking identifier issued for the intended Segment source and save. Verify a permitted test event on the configured site or app and confirm its receipt in that source.

Configure Spoonity​

Open Spoonity. Use the available enablement, vendor ID and platform name fields for the intended account. Save and review the stored configuration. Run a test loyalty action and check points or rewards separately in the appropriate provider account.

Verify each boundary separately​

Keep configuration, provider behavior, and user outcomes separate:

BoundaryEvidence to confirmWhat it does not prove
Dashboard configurationThe intended fields and saved values are shown for the intended project.That a provider accepts, authorizes, or can use the configuration.
Provider accountThe provider owner confirms the account-specific setup through the approved channel.That Dashboard sent data or that every future request will succeed.
AnalyticsAn approved synthetic test produces the expected authorized evidence.That all user interactions, orders, or customer data are collected correctly.
Loyalty workflowAn approved synthetic test shows the expected authorized provider result.That points, rewards, eligibility, payments, or customer notifications are complete.
User outcomeThe approved flow shows the intended result for the correct test account and channel.That a save response alone changed access, account state, an order, or a payment.

If a provider, field, or section is missing, do not work around it by adding an identifier to another setting. Resolve the intended connection with the responsible provider and Dashboard owners.

For the product overview of Segment tracking, see Segment on Ordering.co.


Related guides: Settings categories · Developers · Settings overview