Have noticed the activity reports v2 api returns updated completions data after a delay may be like a day or 2.
So, just wanted to know what is the expected delay time frame for data sync in linkedin v2 api's.
Was expecting linkedin v2 api documentation to have the expected delay for activity reports api's , unfortunately couldn't find any such information
Related
I'm trying to get the most recently updated cases from ServiceNow, using the REST API.
I know I can run this call: /api/sn_customerservice/{api_version}/case?sys_updated_on>={given date}
The problem is that some background process updates the sys_updated_on field for many cases that don't actually have any activity on them. So a case that has a last activity from 2019 may have its sys_updated_on updated today.
I have no access to change the behavior of whatever is updating the sys_updated_on field.
I know I can pull a list of records and then make a second API call to /api/sn_customerservice/{api_version}/case/{id}/activities to check the date of the most recent activity for a given case. But that's two API calls for every case (of which there are thousands).
Is there any way to get a list of just the cases that have had recent activity?
Limitations: this is a personal project and I only have access to the API with my user credentials. I don't have a development account.
The design of Case API is to get case records
The design of activity endpoint within Case API is mainly to get activity stream details of given input case.
The usecase you have is - To get list of cases that have had recent activity. It definitely makes sense to first get the recent activities for all cases in a limited timeline like a day or a week and then only query details of those related cases to the activity stream records.
However to do this you will need to implement a scripted REST API to query sys_journal_field table and get case sys_ids which have recent activity in activity stream.
Having read the REST API documentation, I couldn't find any information related to getting the segment count for a notification. Is it possible to get it using the REST API? Getting the segment count is possible in OneSignal developer panel as you can change the filters and see the estimated number of clients who receive your notification. But I want to get that estimated number using the REST API.
It is not possible to get the estimated receiving users before creating the notification using the REST API. A workaround to this would be creating templates and using the template_id in the API call.
I am building a chrome extension/third-party app that needs to read data from salesforce.
One way is to make a API call directly to salesforce whenever a user needs to query something, but this will create a large number of API calls.
What I attempted to do is to pull a ton of data from salesforce into a Google Sheet using the reports API, on an hourly basis, then query the data through Google App Script. But Salesforce's 2000 row limits for Reports and SOQL API, as well as the runtime limits posed by Google App Script, make my life difficult :(
What are the best ways to get data from salesforce for third party extensions?
Appreciate your help!
The bulk API can fulfill your needs as it hasn't a limitation on the number of returned rows.
I just want to ask you about the Reporting API v4 because I'm seeing different values between API response and web reporting view (Google Analytics dashboard). The metric is unique events.
This is the query using API Explorer
API Explorer query screenshot
And here is the API Explorer result (if you want to see the query, read my first comment below, please notice green and red highlighted)
API Explorer result screenshot
On the other hand I'm using the web report viewer and for unique events I'm always seeing different values (also I used many other filters, with different scenarios, always returning different data in unique events metric), but (the weird thing) is total events value is ok (in all cases). I used the same dates for API and web view calls (also I applied same filters on web reporting, also I tested using other metrics and the values are the same, so there is no layer 8 issue)
Web reporting screenshot
Do you know what's going on here? I don't know which value is correct, I don't know if API or web reporting is failing.
Best.-
Please check this changelog entry - https://developers.google.com/analytics/devguides/changelog#event_tracking and this support article - https://support.google.com/analytics/answer/7084499?hl=en
It's all connected to the changes in unique events-connected metrics from September '16 (you can read more about it on Analytics Blog under "Improving Google Analytics Events with Unique Events" post).
Right now:
WEB UI "Unique Events" = API "ga:uniqueEventsTemporary";
WEB UI "Unique Dimension Combinations" = API
"ga:uniqueDimensionCombinations" and "ga:uniqueEvents".
This is the query using API Explorer (I posted in an answer because I couldn't do in question, only 2 links allowed)
API Explorer query screenshot
I have a custom variable defined on my site and the data is being recorded properly in my Google Analytics account. When I go to access the data via the Google Data Feed Query Explorer, the data I get isn't the same. Really, this is only the case with 'Visits' and any metrics calculated using it.
This is what I see in my dashboard:
http://www.screencast.com/t/QJl21ZOmpw
This is what I see in the query explorer:
http://www.screencast.com/t/WNGLiUUWum
I made sure the time frame matches and have pulled the same metrics. 'Hits' (aka pageviews) match up perfectly every time. Visits is obviously off and seems to be messing up other metrics that depend on it, such as 'Pages/Visit' (aka pageviews per visit).
I have reviewed the code and the custom variable is being set prior to recording the pageview. Am I missing something? My understanding is that Google Uses this exact same API to run their Analytics Dashboard, so why am I getting different data?
Try removing the visitors metric from your feed in the Query Explorer. A "Visitor" is different than a "Visit". I believe the stats of the Google Analytics screenshot have nothing to do with visitors. And including this metric might actually limit your result set to the unique visitors (I think).