The 8th compares to the 14th because they are both the second week in October.Other than creating another date dimension that offsets the date by one week, I don't know what to say. You'd then use the date dimension that works best with the previous date comparison.

Gotcha. Unfortunately I don't have much experience with Azure, but hopefully someone in the community can chime in!

Hi Erik, this idea is currently being discussed by the community: Dynamic date comparison I'd recommend upvoting that idea, and commenting your use case on why it would be valuable for you in reporting.

Arun's link to Attribution IQ would definitely be the one you're looking for.

It sounds like the implementation starting working on the 19th, and was not before then. We can't collect historical data if it wasn't working correctly, so I'm afraid you're out of luck there.I'd recommend focusing on the data from the 19th onward.

Clarification - do you have the Adobe Analytics side working? Is your question geared towards analysis on Azure?

Unique visitors in a hit-level segment should simply equate to a hit-level segment. You can get more granular (visits within a unique visitor), but you can't get less granular (unique visitors within a hit). I believe you'll see similar results if you put page views instead of unique visitors in the...

Launch is simply the platform you use to host Adobe Analytics to send image requests. Ultimately the data will still get in Adobe Analytics, which use the data feed columns in the doc you linked to.Based on your explanation, I do not see any duplication of efforts taking place.

Hi Karthik, are there any follow up questions you'd like to ask?

The Experience Query Service will have a native Tableau integration. Keep an eye out for announcements in the coming months!