Deprecate UA360 Account in favor of GA4 Account
User Story
Google Analytics data has been routed to the UA360 property while we migrated to GA4. Once GA4 is operational, we need to remove the old UA360 property and transfer any user permissions to the new GA4 one.
Acceptance Criteria
- [ ] GIVEN the current UA360 property THEN deprecate usage of the UA360
Sketch
- [ ] Ensure no data is flowing into UA360 after transition to GA4 property
- [ ] Ensure all users in UA360 who need access to GA4 property have it
- [ ] Remove/shutdown UA360 property
@dlennox24 does anything remain here? If this is a clean up thing--can you complete remaining tasks and close?
@hkdctol Here is the list of the GA properties as they stand.
- GSA Data.gov > Resources.data.gov - GA4
- GSA Data.gov > next.data.gov
Ready for deletion with all of UA360: Blocked by the determination of the Wordpress property
- Moving TTS UA Properties to GSA Acq Gateway > Agriculture
- Moving TTS UA Properties to GSA Acq Gateway > All Web Site Data
- Moving TTS UA Properties to GSA Acq Gateway > Catalog
- Moving TTS UA Properties to GSA Acq Gateway > Disasters
- GSA Data.gov > Resources - UA data
- GSA Data.gov > SDG - UA data
- Moving TTS UA Properties to GSA Acq Gateway > Catalog - UA360 data
Pending determination of data retention and deletion:
- GSA Data.gov > Federal Data Strategy - UA
- GSA Data.gov > open.USA.gov - UA
- GSA Data.gov > Project Open Data - UA
- GSA Data.gov > Resouraces.data.gov - UA
- GSA Data.gov > Sustainable Development Goals - U.S. NRP - UA
- Moving TTS UA Properties to GSA Acq Gateway > Wordpress
@dlennox24 Federal Data Strategy--is there any old data to save? Then I would save it, otherwise the list for deletion looks fine.
Per Feb 26th:
- Don't save:
- Wordpress
- Project Open Data
Save the data for the rest and mark for deletion.
@dlennox24 should we close this?