Later stage login

Hey guys, I have a question about how to implement this case using backendless.

  1. the user scan login straight away, or skip the login and do it later, while keeping his aquired coins.
  2. the coins are sent to the backend through an adnetword (there is another question about this):
    http://support.backendless.com/t/is-it-possible-to-write-backend-code
  3. it is possible to identify the user in the ad networks through AdvertisingIdClient which comes with google play services
  4. after the user logins, he needs his user somehow to refer to his coins in the coins table
    so is there a way to generate a temporary row for a user with a userID, and later do a full registration?
    or is there another possible solution?
    Cheers,
    Tal

Create a separate table and call it something like GuestUsers. Store your non-authenticated users there with any related data (coins, etc). Once user registers/logs-in, copy the data from GuestUsers to the user object.

Hey mark.
That could work…I can create a table that maps userID to advertisingId,
but that would mean that then the ad network will Identify him using his advertisingId, instead of his user Id,
which changes some things… like when he switches device/wants to have 2 user on the same device, and other development/schema changes.
Is there a way for backendless to generate a user id for that guest user before he registers?
and later when he registers set it using backendlessUser.setProperty()?

thanks,
Tal

If the ad network assigns another ID to the user, store it as a property in the object representing the user.

Is there a way for backendless to generate a user id for that guest user before he registers?

How is that going to help if the backend generates user id? A userid is nothing but a GUID (a globally unique identifier). Whether we generate one or you do it in your code (client-side or custom biz logic), it makes no difference.

Regards,
Mark