Adobe warehouse segment doesn't work | Community
Skip to main content
li_meng
Level 2
December 1, 2015
Solved

Adobe warehouse segment doesn't work

I have tried with 3 types of segments, but none of them works. There are data in the result but it doesn't consider segment.  Could someone help me?

{
    "reportDescription": {
        "reportSuiteID": "{reportSuiteID}",
        "dateFrom": "2015-10-01",
        "dateTo": "2015-10-01",
        "source": "warehouse",
        "elements": [{
            "id": "browser"
        }],
          "segments":[
            {
                "id":"{segmentId}"
            }
        ],
    }
}

{
    "reportDescription": {
        "reportSuiteID": "{reportSuiteID}",
        "dateFrom": "2015-10-01",
        "dateTo": "2015-10-01",
        "source": "warehouse",
        "elements": [{
            "id": "browser"
        }],
          "segments":[
            {
                "id":"dw:{segmentId}"
            }
        ],
    }
}

{
    "reportDescription": {
        "reportSuiteID": "{reportSuiteID}",
        "dateFrom": "2015-10-01",
        "dateTo": "2015-10-01",
        "source": "warehouse",
        "elements": [{
            "id": "browser"
        }],
       "segment_id":"{segmentId}"
    }
}

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Gigazelle
GigazelleAccepted solution
Employee
December 3, 2015

You will want to use API 1.4 to request this data. Are there any obstacles preventing you from doing so?

View reply

7 replies

li_mengAuthor
Level 2
December 3, 2015

Hi Gigazelle,

I want to use warehouse with segment. But neither segment container nor segment id works. Here is my reportDescription.

{
    "reportDescription": {
        "reportSuiteID": "xxxxxx",
        "dateFrom": "2015-10-01",
        "dateTo": "2015-10-01",
        "source": "warehouse",
        "elements": [{
            "id": "browser"
        }],
        "segments":[
        {
        "id":"s1011_565c65d5e4b000f255c10aa7"
        }]
    }
}

 The segment is created with dashboard and it's available for warehouse. It's a segment browser="Android 4.0", but I can see all the browsers(Chrome,Safari...) in the result. That means the segment can pass the validation but is not used for warehouse. 

Could you tell me the right way to use segment for warehouse? 

Translate
Gigazelle
GigazelleAccepted solution
Employee
December 3, 2015

You will want to use API 1.4 to request this data. Are there any obstacles preventing you from doing so?

Translate
li_mengAuthor
Level 2
December 2, 2015

Excuse me, do you have any news?

Translate
li_mengAuthor
Level 2
December 1, 2015

Hi, 

Here's the details of the segment(https://api.omniture.com/admin/1.4/rest/?method=ReportSuite.GetSegments). I am not sure what is the parameter suite_enabled, because I can not set it in dashboard 15.Maybe it relates with my problem

            {
                "id":"s1011_565c65d5e4b000f255c10aa7",
                "name":"warehouse test6",
                "folder":"",
                "class":"",
                "suite_enabled":false,
                "read_only":false
            }

Translate
TanmayMathur
TanmayMathur
Employee
December 1, 2015

Hi,

Thanks for reaching out.

Could you please give an example what values you are using in place of 'segmentid' in the code snippet? That would help in troubleshooting the problem.

Thanks!

TM

Translate
li_mengAuthor
Level 2
December 1, 2015

Is the segment created with API 1.3 different from the segment created with dashboard version 15? I can find the segment created by API 1.3 on the dashboard 15 but the modification and delete of dashboard have no effect on th segment of API 1.3

Translate
li_mengAuthor
Level 2
December 1, 2015

I am using the API 1.4. I found I can not find segments with the version 1.3 DataWarehouse.GetSegments. It may explain why the first request returns a segment with name null. But is that means a confliction between version 1.3 and 1.4? 

        "segments":[
            {
                "id":"{segmentId}",
                "name":null
            }
        ],

Translate
Terms & ConditionsAccessibility statement

Loading footer...