Create Global Segments that can be applied to multiple report suites

[#1]

After going back and forth wtih a support person, I was told it is NOT possible to create segments that apply to multiple report suites.

Although there are Pre_Configured segments setup that DO work with mutliple reportsuites.

Visits from Paid Search

Single Page Visits

Visits from Natural Search

Visits from Mobile Devices

Visits with Visitor ID Cookie

I simply want to create a segment and apply it to the 20+ reportsuites I have setup under my account.  Right now, the only way to make this work is to create site specific segments.  This creates a lot of extra work when it appears the ability to create segments that can apply to any reportsutie is already avaialable.

[#2]

I understand that an organization might have a multitude of report suites and that those report suites may have different evars from one to another and that as a result Adobe is reluctant to let customers share segments from one suite to the other.  In response to this thought, I have a couple of thoughts of my own:

1) After migrating from SC 14 to SC 15 and running reports that span over the date of migration there is a note that pops up indicating that data before date XXXX is processed under a different platform than data after date XXXX.  Cannot a similar note be populated indicating that segment was created in report suite XXXX and thus may not populate data properly in suite XXXX?  

2) Adobe is not reluctant to not "idiot-proof" other things that may cause devastingly bad data to be seen, such has customizing report suite menus.  Why worry so much about sharing segments, but so little about other issues that could complicate an organizations reporting at least as equally?

3) If adobe is able to see the evar name from report suite to report suite shouldn't it also be able to build in some logic that does not allow the segment to be shared from one report suite to other UNLESS the names are identical.  I view this in much the same manner of the IF function in excel =IF(evar3 in report suite a=evar3 in report suiteb,share,DO NOT SHARE)

Just a few thoughts to attempt to help this issue be expediated.

Thanks,

Mark

[#3]

Allow for segments to be created which work across report suites. So, I can select a segment first, and then select any report suite to which it may apply. It applies especiially for geo-code based segments

[#4]

Yes, the new segmentation filter is going to be useful, but it's going to be frustrating creating the same segment time and again for multiple suites.

[#5]

nah...this would be too confusing

[#6]

It kind of depends on the segment. The ones that you mentioned are applicable to all report suites. But segments that use custom variables are going to differ from suite to suite. eVar5 might be "Internal Search Terms" in one suite, but "E-mail Campaign ID" in another. As I see it, there are two possible reactions to this: 

1.) "Yes, that's a big problem. But you could still have segments that don't use custom variables go across multiple suites."

2.) "That might be a problem for some people, but good implementation governance should cause eVars to be the same across suites, so cross-suite segments should be allowed."

Which do you subscribe to? Or is there a third point of view we should be considering? 

[#7]

Option 2 is what works for me.

2.) "That might be a problem for some people, but good implementation governance should cause eVars to be the same across suites, so cross-suite segments should be allowed."

Leave it up to the Admin to make this decesion.  We don't have 100% parity across all reportsuites on eVar and events, but for key metrics,  we absolutely do.

[#8]

Thanks Mike! 

[#9]

I know that I posted about this several times a few months back, but it seems as if there has been zero progress towards making this happen.  Any word on when this feature may become available?

[#10]

I combined several similar ideas into a single thread here. 

Please continue to provide feedback. This is definitely something that is on our radar, along with a number of other segment management improvements.

[#11]

I agree with point #2 as well- our report suite implementations are standardized, and where there might be a difference in variable usage, the analyst "should" know that the filter is not relevant- so I would vote for this option as we have a ton of consistent report suites that would benefit from this functionality.