Summary
The user is experiencing a discrepancy in the data retrieved from the Iterable connector in Airbyte between the Email Send and PushSend streams. The Email Send stream provides data about campaigns and message IDs, while the PushSend stream only provides customer email, user ID, and createdAt. The user is questioning if this difference is intentional or if both streams should provide the same information.
Question
Hi I am using the Iterable connector to pull data about both push notifications and email notifications. There are multiple streams for both but for this example I will focus on the <Iterable API Documentation Send> (Incremental) and https://api.iterable.com/api/docs#export_exportDataJson|PushSend (Incremental). When I use the email send stream I get data about campaigns and message IDs along with the customer email, user ID and createdAt. When I use the push stream I only get the customer email, user ID and createdAt and nothing else. Is this by design or should both streams give the same information about campaigns etc?
From the documentation here https://docs.airbyte.com/integrations/sources/iterable/ they seem to use exactly the same method to pull data (https://api.iterable.com/api/docs#export_exportDataJson). If I manually make a request using that endpoint I can get information about campaigns etc for push notifications so I can’t understand why it isn’t coming through the connector when both streams on the face of it function in the same way.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.