Should I create relationships between profiles and objects with data pipelines or the Track API v2 ?
The CIO docs have conflicting info:
- Journeys Relationships docs say “Use our Track v1 or v2 APIs to set relationship attributes programmatically”
- But the Connect Journeys data sources to destinations docs say “Use our newer source integrations instead… newer API [aka data pipelines]… support batch… where we’re focusing our development efforts”
I’m confused how/why there are two ways to do the identical thing and which is best practice. Specifically, Track v2 API lets you make a single request OR batch request and include cio_relationships, but the same functionality seems to exist with data pipelines /group POST API call and batch call.
The difference/benefits/best practices are not clear. 🤔 The comment “where we’re focusing our development efforts” above makes it seem like it’s an important distinction for the future to prevent our integrations facing deprecated functionality as well as making sure we can use the latest features.
Thanks!
