Mapping the new alphanumeric Custom Advanced Segment using the numeric ID?

[Stephane]

Hi,

We just saw the advanced segments IDs have been changed to alphanumerics IDs (See July 16 https://developers.google.com/analytics/devguides/reporting/core/v3/changelog ). This impacts many of our queries since we store the segment ID. 

Is there a way for us to find the new segment ID using a numeric ID? For example, what would be the new segment ID for the segment # 1794442974?

Thanks,

Stéphane

[mschenkel]

Stephane,

I have come across the same problem.  I even came across one google profile with mixed values (i.e. older ones still numeric, newer ones alphanumeric).  I can't remember where I saw it, but thought somewhere it was said when a user edits a segment it causes it to be converted to new format.  

I also read somewhere that the numerical formats will soon be deprecated.  So I would advise you to store the original numeric ID if you ever need to map them to the new alphanumeric.

[Nick Mihailovski]

Hi

If you query the reporting API using the old numeric values, the response contains the new alpha ID in the response.query.sements field.

-Nick 

--
You received this message because you are subscribed to the Google Groups "Google Analytics Reporting API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-data-...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Luis Pereira]

Would it make sense that the Management.segments returned both the old and new IDs? It would really make things much easier.

Many thanks,

Luis

2013/9/25 Nick Mihailovski <n...@google.com>

[Nick Mihailovski]

Right now you can update the saved segments as your clients use their advanced segments in the reporting API.

You can proactively query the reporting API to get a translation.

You can just update the saved segments with new Mgmt API response.

Since the segments response is all user driven from what is saved in the Mgmt UI, I'm curious why you are saving segment IDs? How does your app handle when users adds a new, or deletes an existing segment?

-Nick

[Luis Pereira]

Nick, we are a bit confused about the new segment IDs conversion process.

We are using a couple of accounts, and so far, all of our segments have the old numeric IDs when using the Management.segments.

I assume you must be running some kind of migration process that will replace the current advanced segments with the new segmentation. Is it the case? If so:

1. Once the migration is done with an account, will the old numeric IDs be replaced by the new alphanumeric IDs?

2. Once the migration is done with an account, will the Management.segments immediately start returning the new alphanumeric IDs assigned to the old advanced segments?

3. Are account administrators notified some way about the moment the migration starts and finishes?

4. Is the migration affecting to web properties using just analytics.js (Universal Analytics)? Or also to web properties using ga.js (Classic Analytics)?

Many thanks in advance,

Luis

[Nick]

comments inline:

On Tuesday, October 1, 2013 11:05:49 AM UTC-7, Luis wrote:

Nick, we are a bit confused about the new segment IDs conversion process.

We are using a couple of accounts, and so far, all of our segments have the old numeric IDs when using the Management.segments.

I assume you must be running some kind of migration process that will replace the current advanced segments with the new segmentation. Is it the case? If so:

There is no process, we made this change a while ago.

 

1. Once the migration is done with an account, will the old numeric IDs be replaced by the new alphanumeric IDs?

yes the management.segments will return new alphanumerics Ids 

 

2. Once the migration is done with an account, will the Management.segments immediately start returning the new alphanumeric IDs assigned to the old advanced segments?

yes

 

3. Are account administrators notified some way about the moment the migration starts and finishes?

yes through the changelog: https://developers.google.com/analytics/devguides/config/mgmt/v3/changelog

 

4. Is the migration affecting to web properties using just analytics.js (Universal Analytics)? Or also to web properties using ga.js (Classic Analytics)?

All segments.

 

Many thanks in advance,

Luis

2013/9/25 Nick Mihailovski <n...@google.com>

Right now you can update the saved segments as your clients use their advanced segments in the reporting API.

You can proactively query the reporting API to get a translation.

You can just update the saved segments with new Mgmt API response.

Since the segments response is all user driven from what is saved in the Mgmt UI, I'm curious why you are saving segment IDs? How does your app handle when users adds a new, or deletes an existing segment?

-Nick

On Wed, Sep 25, 2013 at 3:50 AM, Luis Pereira <l.pereira...@gmail.com> wrote:

Would it make sense that the Management.segments returned both the old and new IDs? It would really make things much easier.

Many thanks,

Luis

2013/9/25 Nick Mihailovski <n...@google.com>

Hi

If you query the reporting API using the old numeric values, the response contains the new alpha ID in the response.query.sements field.

-Nick 

On Tue, Sep 3, 2013 at 9:19 AM, Stephane <step...@dashthis.com> wrote:

Hi,

We just saw the advanced segments IDs have been changed to alphanumerics IDs (See July 16 https://developers.google.com/analytics/devguides/reporting/core/v3/changelog ). This impacts many of our queries since we store the segment ID. 

Is there a way for us to find the new segment ID using a numeric ID? For example, what would be the new segment ID for the segment # 1794442974?

Thanks,

Stéphane

--
You received this message because you are subscribed to the Google Groups "Google Analytics Reporting API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-data-export-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Analytics Reporting API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-data-export-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Analytics Reporting API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-data-export-api+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Analytics Reporting API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-analytics-data-export-api+unsubscribe@googlegroups.com.