Hi,
Thank you for getting back to us.
After reviewing your concern, I understand that you are getting different
campaign records when including the segment.date field in the SELECT columns or
only use segments.date in the WHERE clause. To investigate further, could you
provide the complete req
yes i did all that of course. for example i found out by trial and error
and pure inference (nothing in the docs) that a paused campaign doesn't
really have a segment.date so when filtering on a specific date, you
actually only get the active campaigns. that's what i infer from the
results but
No answer yet?
The significance of the segments.date column seems something that should be
documented better. In a different use case I now understand that there is
no querying of campaign states by date - even though doing so does not give
any error and simply falsely returns whatever date is
Hi,
I'm struggling to understand why I am getting a vastly different number of
campaigns depending on whether I add the field segments.date to the select
columns or only use segments.date in the where clause?
>From the documentation i understood that there is no need to use
segments.date in t
