I have a React website, I want to build a system that first a code is created for example its "my-special-code-100". I want to track website visitors who entered the website from a url like https://mywebsite.com/../?code=my-special-code-100 and need to track if or if not X 'not signed in' visitor do a successful payment - a button click on specific page - also need to store an account id of the wallet, payment that happened, and need to see trackings of how many visitors of website came with "my-special-code-100"(and other codes) and how many of them made a payment and stored wallet id should be visible for that visited user.
I couldn't be sure how to and is Google Analytics correct tool for this and could you give example what can I use to achieve something like this ? Thanks
Related
Is it possible to get a current users acquisition channel ( Facebook, Glassdoor, etc... ) and append it to a string during an onSubmit?
We have a careers page on our site with a search form that when filled out and submitted takes the user to a 3rd party software we use for our job listings. What we would like to do is track the users that submitted that form so we can see what channel lead to them looking for a job.
Ex:
User visits our Facebook page and clicks link to our site. Once on our site they fill out the job search form and is sent to our jobs listing site. We use JS to create the onSumbit url and fill it with the fields they answered and would like add another "acquisition" parameter to it with said acquisition.
You can store the referrer in a cookie if this is different from the domain of your website. In this way you can know where the user came from and use that value in the string you send to submit.
I have setup my application in google analytics.
App information :
Angular 1.4.10,
Google analytics setup.
Question :
When I was tracking the page views I see even URL related to the api calls are recorded.
Anyone know why is it recording API/Calls and due to which all the API calls are making to the top visited . We are not able to track proper page visits.
Example:
website is ww.abcd.com
api call are /api/getsearch
redirect page : www.abcd.com/search?keyword=something
real time page views are recorded as both:
/api/getsearch
/search?keyword=something
Do any one know why these calls are recorded and why are these recorded in the page views and how to not record them.
I am exposing a page with a standardcontroller="account" to a force.com site facing the public. This page displays account specific data to the clients. Now when a customer logs in to my website I want him to have access to his account's data and only his account data. Here is the problem; the url for a page with a standardcontroller has a Id field, such as "https//www.myforcesite.force.com/AccountViewPage?Id=a82347dod". If a user changes a few keys on the Id, it is very easy for him to access other people's account page and bypass the login process. How can I prevent that.
I opened a ticket with salesforce but they told me its working as intended. I don't think a vulnerability to a trivial brute force attack should be intended so I want to know if there are any fixes?
Create one StandardController extension and check if the logged user in your website has the permission to view that account.
http://www.salesforce.com/us/developer/docs/pages/Content/apex_pages_standardcontroller.htm
What you are looking for is URL rewriting for force.com site.
For example, let's say that you have a blog site. Without URL rewriting, a blog entry's URL might look like this: http://myblog.force.com/posts?id=003D000000Q0PcN
With URL rewriting, your users can access blog posts by date and
title, say, instead of by record ID. The URL for one of your New
Year's Eve posts might be:
http://myblog.force.com/posts/2009/12/31/auld-lang-syne
I want to create a one page site that will use Facebook Connect and allow my friends to reserve a spot for an upcoming event. Using there Facebook ID I would like my friends to pay(reserve) a spot and then show their Facebook picture in the spot they reserved. Sort of like Meetup.com when you RSVP except its a one page site and for a one time event. Can I build this only using front-end technologies or do I need a backend?
The answer is yes, you will need a back end system to store the paid registrants, print out a list of paid users to have at the door of the event to make sure they paid, store the user id to be able to display their picture, etc. etc. etc.
I am working on a chrome bookmarking extension with google app engine as the backend. I am the only user now but I thought that if in the future there are other users the url needs to include the user name for the extension to interact with the backend. So I was thinking to change
http://ting-1.appspot.com/useradminpage
to
http://ting-1.appspot.com/user_name/useradminpage
where "user_name" is the gmail user id.
But I looked at twitter url and I see that they have
http://twitter.com/#!/user_name/
What is the purpose of "#!"? Is my scheme good enough in this case?
The # in a URL signifies the 'fragment identifier'. Historically this has been used to identify a part of a document identified by an 'anchor' tag, but recently webapp developers have begun to use it to pass information about the page state to Javascript code running in the page. This is used because it's possible for Javascript code to modify the fragment of the current page without causing the page to reload - meaning it can update as you browse through the webapp, and go right back to where you were when you reload the page.
The fragment is not sent to the server when the browser loads a page, so Twitter's server just sees a request for twitter.com; it's up to the Javascript code in the page to examine the fragment and determine what to do after that.
In your particular case, assuming you're using the App Engine User service to authenticate users, you have a number of options for how to distinguish users in your URLs:
Use their email address. In theory this can change, and users may not want their address in a URL they will share. If the URLs are private, this is more or less a moot point.
Use their user_id. This is opaque and reveals no useful information about the user, so it's safe, but it's also meaningless and hard to remember.
Let users pick a nickname for their URLs, like Facebook and other services do, on a first-in, first-served basis.