New here? This page is a configuration reference for teams implementing the Stamped.io integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
These are the known limitations of the Stamped.io integration. They are inherent to the current design of the integration and the capabilities of the Stamped.io API at the time this documentation was written, and they apply to all subscribers.
Platform Scope and Tested Versions
Remote platform: Stamped.io, integrated through the Stamped.io API (version 2) at its documented base URL (for example, https://stamped.io). See the Stamped.io developer documentation at https://developers.stamped.io for current API details.
Direction: customer data flows from iPaaS.com to Stamped.io.
Last tested end-to-end: 2026-06-25, against the Stamped.io API as documented in production at that date.
Not built for: this integration is built specifically for Stamped.io's review and loyalty platform. It is not built for any other vendor product, and if Stamped.io introduces a separate product line or a materially different API version in the future, this integration will not automatically support it.
1. Customer data flows in one direction only
The integration writes customers from iPaaS.com to Stamped.io. It does not read or poll customers that originate or change in Stamped.io.
What this means for you: Stamped.io is kept up to date from the customer data held in iPaaS.com. Changes made directly in Stamped.io are not pulled back into iPaaS.com. Treat iPaaS.com as the source of truth for the mapped customer fields.
2. Customer deletion is not propagated
Stamped.io does not provide a way to delete a customer through its API, so the integration does not remove customers from Stamped.io.
What this means for you: Removing a customer in iPaaS.com does not delete the corresponding Stamped.io customer. Manage customer removal directly in Stamped.io when needed.
3. Updates send only the mapped fields
When a customer is updated, the integration sends the fields populated by the mapping and omits fields that are not mapped, rather than sending empty values for them.
What this means for you: The mapped fields in iPaaS.com are the source of truth and are refreshed on every transfer. Whether Stamped.io preserves or clears a field that the integration does not send is determined by Stamped.io's own update behavior; subscribers or their MiSP should validate this in a staging environment before relying on it in production.
Note: This behavior is specific to the customer update path.
4. Subscription state is reconciled by a separate step
Stamped.io does not change a customer's survey and review-email subscription state as part of an ordinary customer update. When the subscription field is mapped, the integration makes a dedicated follow-up call to subscribe or unsubscribe the customer so the state matches the mapped value.
What this means for you: To control whether a customer is subscribed to Stamped.io surveys and review-request emails, map the subscription field (for example, as a Static value). When the field is left unmapped, the customer's existing subscription state in Stamped.io is left unchanged.
5. Selectable collision handling is not offered
This integration does not present selectable collision-handling methods for the customer collection. Records are matched and linked by external ID and by customer email.
What this means for you: There is no per-collection collision-method choice to configure. Ensure the customer email is mapped so Stamped.io can match an existing customer rather than create a duplicate.
6. Connection validity is confirmed on first transfer
The integration treats the connection as established once the credentials are saved; invalid credentials surface as an error on the first transfer rather than at the moment the connection is saved.
What this means for you: After configuring the connection, run a transfer (for example, a Manual Sync of one customer) to confirm the credentials are correct. If the credentials are wrong, the error appears in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
This document covers 6 known limitations. For detailed, per-collection behavior, see the mapping collection description for the customer collection.