# Track Button Click by Signed In User

**URL:** <https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163>\
**Category:** Ask for Help\
**Created:** [February 3, 2021, 7:56am UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163 "2021-02-03T07:56:44Z")\
**Posts on this page:** 8\
**Page:** 3

<div class="post-metadata">

**Author:** ![ehdubya](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ehdubya/32/24087_2.png) [@ehdubya](https://community.glideapps.com/u/ehdubya)\
**Post date:** [February 4, 2021, 3:11pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/42 "2021-02-04T15:11:04Z")

</div>

I’m quite sure we have a similar app/setup…we decided to let the Business Owners decide on expiry dates and # of offer claims available, however we update them in-app/in-sheet. We have more control that way, however tedious it may be.

So that yes, only 100 offers are available, and no matter when someone claims an offer, it will always expire at the end of the month (thanks to Jeff Hager’s glide/math wizardry, Darren knows what I’m talking about 😜🤓).

---

<div class="post-metadata">

**Author:** ![Jen\_NYCP](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@Jen\_NYCP](https://community.glideapps.com/u/Jen_NYCP)\
**Post date:** [February 4, 2021, 3:13pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/43 "2021-02-04T15:13:25Z")

</div>

Oh nice! Yup, I will be discussing dates of numbers with the owner.

For the number of offers available, you just add that number to your ‘available’ column right?

---

<div class="post-metadata">

**Author:** ![Jen\_NYCP](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@Jen\_NYCP](https://community.glideapps.com/u/Jen_NYCP)\
**Post date:** [February 4, 2021, 3:15pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/44 "2021-02-04T15:15:51Z")

</div>

> [@Darren\_Murphy](#):
>
> This table will contain one row per user, per offer redeemed, and should contain least 3 columns:
> 
> - User ID (a value that uniquely identifies each user, and will allow you to create a relation back to your User Profiles sheet. I’d recommend using the RowID)
> - Offer ID (same as above, but to your Offers sheet)

How will I bring these two ID’s over? I know probably not google sheet array since I got mixed up on favorites with that. 😌

---

<div class="post-metadata">

**Author:** ![ehdubya](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ehdubya/32/24087_2.png) [@ehdubya](https://community.glideapps.com/u/ehdubya)\
**Post date:** [February 4, 2021, 3:18pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/45 "2021-02-04T15:18:46Z")

</div>

Yes. We also have all the offers in an inline list, so that if “available” of a specific offer = 0, then it is filtered out of the inline list (then users won’t get excited to see…an unavailable offer 😳).

---

<div class="post-metadata">

**Author:** ![Mishta\_P](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mishta_p/32/16900_2.png) [@Mishta\_P](https://community.glideapps.com/u/Mishta_P)\
**Post date:** [February 4, 2021, 3:19pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/46 "2021-02-04T15:19:20Z")

</div>

Like @Darren_Murphy said, it is worth thinking about everything you might possibly want to do with an offer, and build in an option for them all (unless there are any that are ruled out completely).

Far easier that, than having to add them after the event. I’ve just come up with an idea with the app I’m building, it is going to take a bit of work, but will give me far more flexibility down the road.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 4, 2021, 3:26pm UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/47 "2021-02-04T15:26:49Z")

</div>

You don’t “bring them over”, they will already be there when you add each row to that table…

> [@Darren\_Murphy](#):
>
> When a user taps the button to redeem an offer, change your action so that it adds a new row to your Redemptions table:
> 
> - UserID (whatever you use to uniquely identify the user)
> - OfferID (ditto for Offers)
> - Redeemed At (current date/time stamp)

When you use the “Add Row” action, you have the option to use any column from your User Profiles sheet.

---

<div class="post-metadata">

**Author:** ![Jen\_NYCP](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@Jen\_NYCP](https://community.glideapps.com/u/Jen_NYCP)\
**Post date:** [February 7, 2021, 8:56am UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/48 "2021-02-07T08:56:36Z")

</div>

> [@Darren\_Murphy](#):
>
> The counter to track how many times each offer has been redeemed is no longer necessary, as you can do the following:
> 
> - Create a multi-relation between your Offers & Redemptions sheets (Offers.ID → Redemptions.OfferID)
> - Then create a Rollup column in your Offers sheet through that relation (relation → OfferID → count). This will give you a count for each offer.

Instead of this can I just keep the available column in the offers sheet? Essentially just adding an ‘add row’ action to redeemtion sheet to the multiaction.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 7, 2021, 11:17am UTC](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163/49 "2021-02-07T11:17:49Z")

</div>

Yes, that should be okay.

[Previous page](https://community.glideapps.com/t/track-button-click-by-signed-in-user/22163.md?page=2)
