It is one of the common question while opting the Web Analytics tool and doing the comparison is very common and first action done by business owners.
- Customizable Intuitive dashboards
- Data sharing is not very easy with other users
- Works well with data analysis languages like R and Python.
- CRM integration not possible
- Free tool for the first 10 million hits, post that about $150,000 (for over 1 billion hits).
- No dedicated customer support team
- Free Version is available
Adobe Analytics (formerly known as SiteCatalyst – Omniture)
- Implementation is easy but requires some technical assistance and little programming knowledge.
- Server Side and Client-side implementation is possible
- Less intuitive in reporting
- Much easier to share with other users.
- Highly customizable
- Market Leader
- Third-party integration is available through various options
- 24×7 Dedicated customer support.
- CRM integration allowed
- No free version is available
- Each server call is charged
Google Analytics is good if you don’t have a large analytics and tech team, Adobe works mainly in large digital-first / e-commerce companies with dedicated analytics and tech teams. Adobe Analytics is for serious business and long term business as it is part of Adobe Experience Cloud. Adobe Analytics has a market share of 39% in Housewares/Home Furnishings, 36% in Food/Drug, 39% in Books/Music/ Video, and 41% in Mass Merchants.
There are 2 methods to get this:
NewRepeat can be captured through segment or through plugin
With the help of Segment:
Basically we are looking at the visit number of the visitors: if a visitor has at least one visit with a visit number higher than 1 (2 or higher) the visitor is segmented as “returning visitor”. All others are segmented as new visitors. Be aware that this is not depending on the timeframe you are looking at rather segmenting the visitors in their whole history i.e it would be dependent on ECID cookie…which is set for 2 years
With the help of Plugin:
Using plugin you can set your own cookie and set it according to your own time, which is generally 30 days, but can be anything as per the business vertical requirement.
While tools/services one uses depend on the need and several other factors. I will share a few popular ones often used by Digital Analytics professionals.
- Web/App Analytics – Google Analytics, Adobe Analytics, GA(App+Web, Firebase)
- Dynamic Tag Management – Google Tag Manager, Adobe Launch, Tealium, Ensighten
- Analysis – Excel, SAS
- Debugging dataLayer – DataLayer Checker, GA Debugger, FB pixel helper
- Reporting & Visualization – Google Data Studio, Tableau, PowerBI, Tibco Spotfire
- Product/Event Analytics – Mixpanel, GA(App+Web)
- Engagement/Marketing Automation – WebEngage, MoEngage
- App Attribution – Appsflyer, Branch
- Session Recording – Hotjar, Full Story
- Marketing warehouse – Google Bigquery
- Email – Mailchimp, Sendgrid / SES
- CRM – Hubspot, Salesforce
- CDP – Segment
To dig deeper into data/Tech
- API Testing – Postman
- Data Lake – S3, GCS
- Data Warehouse – Postgres, Redshift
- ETL – AWS Glue
- Querying S3 data lake – Amazon Athena
- VCS – Git
- Executing code – Jupyter Notebook(Python), R Studio(R)
- Hosting Notebooks – Google Colab
- SQL Client – Dbeaver (connect/query DWH)
- Editor – VS Code, Sublime T3
In the future, I will share more example, Feel free to comment that which tool you use and why.
No matter how many domains a company has they can use the same tracking server for all the domain which is third party cookie implementation.
But if you want the cookies to be created on the domain and want First Party Cookie Implementation then there can be two approaches to handle the situation.
Suppose : They you have 10+ different domain
Where we have to configure 10+ separate tracking server values for respective domains.
Tracking server secure value like smetrics.abc.com for all the 10+ domains – in this case, except for the main domain, the rest would become the friendly third party implementation.
Friendly 3rd-party cookies: Used primarily by organizations with multiple domains that want to use a single visitor ID across all tracked sites. For example, an organization that owns both example.com and example.net could store the cookie on metrics.example.com
As per https://docs.adobe.com/content/help/en/id-service/using/reference/ecid-library-methods.html “the reason for the shift of ECID to CNAME implementations is for persistent visitor identification, not multi-domain tracking”
Option 1 is the best choice here –
It allows for more persistent visitor identification (with option 2, we don’t get a 1st party cookie set server-side)
If there are links that lead for instance from domain X to domain Y, then use appendVisitorIDsTo method for cross-domain tracking
Option 2 doesn’t provide much benefit
First Party Cookie implementation is very much required to mitigate the impact of ITP 2.x