Skip to content
This repository has been archived by the owner. It is now read-only.

QueueDataWarehouse now supports multiple segments #239

Closed
slin30 opened this issue May 7, 2018 · 1 comment
Closed

QueueDataWarehouse now supports multiple segments #239

slin30 opened this issue May 7, 2018 · 1 comment

Comments

@slin30
Copy link
Contributor

@slin30 slin30 commented May 7, 2018

Have tested multiple times now, with up to four simple segments via the segment.id arg. I assume this is yet another undocumented change, as the referenced page in the function doc:

https://marketing.adobe.com/developer/documentation/data-warehouse/r-report-2

...no longer exists.

I assume the limitations here (all) still apply:

https://marketing.adobe.com/resources/help/en_US/analytics/segment/seg_compatibility.html

The tests I performed all use single-container segments with rules all ANDed or ORd together.

The generic call structure I've used successfully to date (not to say other variations won't work-- but this is all I've tried thus far):

List of 10
 $ date.granularity: chr "year"
 $ date.from       : Date[1:1], format: "2017-04-01"
 $ date.to         : Date[1:1], format: "2018-03-31"
 $ reportsuite.id  : chr "xxxxx"
 $ metrics         : chr [1:2] "uniquevisitors" "visits"
 $ elements        : chr [1:2] "xxxx" "xxxx"
 $ enqueueOnly     : logi TRUE
 $ validate        : logi FALSE
 $ segment.id      : chr [1:4] "segID_01" "segID_02" "segID_03" "segID_04"
 $ ftp             :List of 6
  ..$ host     : chr "ftp.xyz.com"
  ..$ port     : chr "21"
  ..$ username : chr "me"
  ..$ password : chr "mypassword"
  ..$ directory: chr "/mydir/"
  ..$ filename : chr "myfile.csv"
@randyzwitch
Copy link
Owner

@randyzwitch randyzwitch commented Nov 4, 2019

I believe this is closed by #248, but if not, let me know and I'll re-open

@randyzwitch randyzwitch closed this Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants