Here is a little explanation from Google about (not set) and (not provided).
Not Set vs Not Provided Not Set: The ‘keyword’ (not set) simply identifies traffic that doesn’t arrive via a particular keyword and hence may not come via any search at all. This includes traffic coming from email, referral sites, or even things like Google Images. Not Provided: The keyword (not provided) describes organic searches that are being hidden from your view, to provide a measure of privacy for users. In 2011, Google began encrypting results from SSL searches (secure searches from users who are logged in to their Google Accounts or using the Firefox search bar)
So, If you see (not set) or (not provided) in Google analytics campaigns add-on, Dashboard or any other place within Analytify plugins, consider that this (not set) or (not provided) traffic is not from particular keyword.
If you know any other explanation of this, please share with us in comment.
From version 2.0 We have added a separate Help tab in Analytify->settings page. Help tab has a support form which is active only if you have Pro version. Your licenses should be active and not expired. It is our priority support form and we respond to these queries faster than ever.
If there is a problem in submitting this form. You can reach our to our support email but It would be easy for us to sort our the support queue if you ask for you support from Help tab.
According to Google: This error Indicates that user has exceeded the daily quota (either per project or per view (profile)).
You would see “(403) Daily Limit Exceeded” error response when Analytify tries to fetch the data from Google analytics and it hits the daily limit quota. Google analytics has limits on their data per day and per website profile. Remember, we are using our own default API keys.
We highly recommend to use your own API keys. So, you don't run into these quota exceeded errors. We have a detailed guide written for creating Google console project and generate API keys which you can use in plugin Analytify->settings page at advanced tab. Simply tick the checkbox and add your details.
If you are still unable to create API keys. We have a paid service to setup API keys for you.
For tracking the users across multiple domains in Google Analytics, It is being recommended by Google to use official Linker plugin instead of setting up Cross-domain tracking yourself. So, at Analytify, We have added an easy way for you to set up cross-domain tracking.
We support analytics.js i.e Universal Analytics tracking only as Traditional ga.js tracking has been deprecated by Google.
Let's say you have 2 sites with name source.com and destination.com. The first step is to install and set up analytify on both WordPress sites as shown below in pictures. Note carefully about the code snippet added in Custom JS Code text areas. You have to link each site to their connected sites. e.g.
On source.com: ga('linker:autoLink', ['destination.com']);
On destination.com: ga('linker:autoLink', ['source.com']);
Note: Do not add http/https with the domain name.
What If you want to set up Cross-domain tracking on sites NOT on WordPress?
Check out the following example:
Let say you have two sites i.e. site-1.com and site-2.com Not on WordPress. To integrate the cross-domain tracking add the below code in the header of each site respectively. Remember to include the Google Analytics code snippet as well.